window.opener is null when an extension page is opened by a non-extension page
Reported by
te...@teemuremes.com,
Apr 23 2016
|
||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.87 Safari/537.36
Steps to reproduce the problem:
1. Call window.open('chrome-extension://your_extensions_id/some_page.html') from a non-extension page
2. Try to reference window.opener in the extension page
3. It returns null instead of the desired Window object
"some_page.html" needs to be listed as web accessible in the extension's manifest, or it won't be opened at all.
I have attached a sample extension that reproduces the problem. Once installed, just click the extension's browser action.
What is the expected behavior?
window.opener has to return the Window object of the opener, not null
What went wrong?
window.opener returned null, not the Window object
Did this work before? N/A
Chrome version: 50.0.2661.87 Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0
This is similar to issue 92669 , but "the other way around".
,
May 6 2016
I don't believe this is loader related. Remove the component.
,
May 6 2016
I'm not familiar enough with the finer details of when window.opener. On normal web pages, this works, though access to that window object is pretty restricted if it's cross-origin. Nasko, what would you expect to happen with extension pages like this?
,
May 8 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Apr 25 2016