Re: Issue 89967 in chromium: window.opener = null when opened with chrome.windows.create (even same-domain)

[chro...@googlecode.com]

Comment #1 on issue 89967 by k...@karlbright.org: window.opener = null when
opened with chrome.windows.create (even same-domain)
http://code.google.com/p/chromium/issues/detail?id=89967

This is also the case when using window.open, the javascript native method

[chro...@googlecode.com]

Comment #7 on issue 89967 by nk...@google.com: window.opener = null when

opened with chrome.windows.create (even same-domain)
http://code.google.com/p/chromium/issues/detail?id=89967

No. We are rendering into this page from another page, so we need to be
able to pass a window object directly. We can't send json through the
DOM. This bug could also address this situation:
http://code.google.com/p/chromium/issues/detail?id=70866

[chro...@googlecode.com]

Comment #10 on issue 89967 by aba...@chromium.org: window.opener = null

when opened with chrome.windows.create (even same-domain)
http://code.google.com/p/chromium/issues/detail?id=89967

From a security & process mode point of view, as long as the URL of the
created window is from the chrome-extension scheme, you can (and should)
put it in the extension process. Once the page is in the extension's
process, you can choose whether to set the opener to null or whatever
window you like. (There may be other considerations, but either our
current behavior or the requested behavior is fine w.r.t. security/process
model.)

[chro...@googlecode.com]

Comment #16 on issue 89967 by bugdro...@chromium.org: window.opener = null

when opened with chrome.windows.create (even same-domain)

http://code.google.com/p/chromium/issues/detail?id=89967#c16

The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=94234

------------------------------------------------------------------------
r94234 | mih...@chromium.org | Tue Jul 26 18:56:38 PDT 2011

Changed paths:
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/api_test/window_open/opener/check-opener.html?r1=94234&r2=94233&pathrev=94234
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/api_test/window_open/opener?r1=94234&r2=94233&pathrev=94234
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/api_test/window_open/opener/set-name.html?r1=94234&r2=94233&pathrev=94234
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/api_test/window_open/opener/manifest.json?r1=94234&r2=94233&pathrev=94234
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/api_test/window_open/opener/test.html?r1=94234&r2=94233&pathrev=94234
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/window_open_apitest.cc?r1=94234&r2=94233&pathrev=94234

Add a test for the workaround for bug 89967.

BUG=89967
TEST=no
R=aba...@chromium.org

Review URL: http://codereview.chromium.org/7497024
------------------------------------------------------------------------

[chro...@googlecode.com]

Updates:
Status: WontFix

Comment #18 on issue 89967 by nk...@chromium.org: window.opener = null when

opened with chrome.windows.create (even same-domain)
http://code.google.com/p/chromium/issues/detail?id=89967

The workaround is sufficient for us. Thanks for working with us to develop
it.