`chrome.tabs.sendMessage` documentation is incomplete
Reported by
natalie....@gmail.com,
Jul 10 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:47.0) Gecko/20100101 Firefox/47.0 Steps to reproduce the problem: Documentation for `chrome.tabs.sendMessage` [1] says "Sends a single message to the content script(s) in the specified tab", but it works for extension pages in tabs too. 1. Open an extension page in a tab. An Options page will do. 2. Add to it an `onMessage` event listener 3. Send a message to the tab with `tabs.sendMessage`, and then a message to the page with `runtime.sendMessage`. 4. The extension page's `onMessage` listener receives both messages. What is the expected behavior? What went wrong? The documentation suggests that `tabs.sendMessage` can only reach content scripts, but it can reach extension pages in tabs as well. Did this work before? N/A Chrome version: 51.0.2704.79 Channel: stable OS Version: Flash Version: [1] https://developer.chrome.com/extensions/tabs#method-sendMessage
,
Aug 3 2016
,
Aug 4 2016
,
Sep 1 2016
,
Sep 4 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by durga.behera@chromium.org
, Jul 11 2016Labels: Te-NeedsFurtherTriage