New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 820874 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

Sometimes content scripts can ignore chrome.tabs.sendMessage

Reported by labobol...@gmail.com, Mar 12 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36

Steps to reproduce the problem:
1. Test URL: https://torrentfreak.com/camcording-piracy-is-dropping-but-not-in-russia-180311/

2. Be quick to scroll down and click the number to show the comments.

3. Select text in either the article text or in the comments. Use keyboard shortcut: CTRL+SHIFT+S it should start to speak the selected text.

What is the expected behavior?
Start to speak the selected text when using the keyboard shortcut.

What went wrong?
Somehow the message from the extension do not reach the content script.

Did this work before? No 

Does this work in other browsers? N/A

Chrome version: 64.0.3282.167  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

Now remember this is flaky. you may have to enable/disable it and/or use incognito mode. Usually it is the content script in an iframe that do not respond as expected. Sometimes it is the other way around.

Added a context menu item to show that the extension is indeed enabled, running and functioning (when using a different way of obtaining the selected text).
 
Speak.zip
29.2 KB Download
You may have to manually setup the keyboard shortcut in chrome://extensions at the bottom in "Keyboard shortcuts".
Labels: Needs-Triage-M64
Components: -Blink>Messaging Platform>Extensions
chrome.tabs.sendMessage is an extensions API.
Labels: Needs-Bisect
Labels: -Type-Bug -Pri-2 -Needs-Bisect Target-67 M-68 RegressedIn-64 Target-66 Triaged-ET FoundIn-66 FoundIn-67 Target-68 FoundIn-68 hasbisect Pri-1 Type-Bug-Regression
Owner: ortuno@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows 10 using chrome latest stable #65.0.3325.181 and latest canary #68.0.3397.0. Issue is not seen in OS-mac and OS-linux.

Bisect Information:
=====================
Good build: 64.0.3277.0
Bad Build : 64.0.3278.0

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/603b79c2d4979cfb871ec7b9b45f66dfba6aa0d4..d487043f96cb39e2fc405cb7369257dcd432de4e

From the above change log suspecting below change
Change-Id: Ic8436e07c888c72d286352345f5ec134c3e3a640
Reviewed-on: https://chromium-review.googlesource.com/786690

ortuno@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks...!!

Comment 6 by ortuno@chromium.org, Apr 16 2018

Owner: krajshree@chromium.org
That change affects tests only. There should be no change in behavior. I suggest trying to bisect this further, since, as reporter mentioned, the repro case is flaky.

Sign in to add a comment