Closed Bug 1286002 Opened 8 years ago Closed 8 years ago

web extensions chrome.tabs.executeScript on about:blank window throws error No Matching Window

Categories

(WebExtensions :: Untriaged, defect)

Product:
WebExtensions
Component:
Untriaged
Version:
49 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1272890

People

(Reporter: droland, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce:

1. Create a manifest with permission <all_urls>
1. Add a listener for chrome.webNavigation.onCommitted
2. Load page http://www.bluedot.com (this page generates two about:blank iframes)
3. The onCommitted listener is called once for each about:blank iframe.
4. The listener calls chrome.tabs.executeScript with tabId from details object provided by onCommitted listener caller and object {frameId:<frameId>, matchAboutBlank:true}.


Actual results:

Async executeScript call returns a chrome.runtime.lastError of "No matching window". The script is not executed in the window.


Expected results:

The executeScript call should succeed. chrome.runtime.lastError should be null.
Additional details:
* Manifest permissions also include webNavigation and tabs
Component: Untriaged → WebExtensions
Product: Firefox → Toolkit
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.