W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2014

[whatwg] Effect on window.opener when navigating an existing window using window.open

From: Bob Owen <bobowencode@gmail.com>
Date: Mon, 3 Mar 2014 11:04:04 +0000
Message-ID: <CA+dJEEAS0O79Ko7QrxXKE8YxaVZha5Hzr_bqpAaJrb2PKHQggA@mail.gmail.com>
To: whatwg@whatwg.org

The spec at [1] and [2] seems to be fairly clear that if an existing window
is navigated using window.open, by a browsing context that is not the
original opener, then window.opener should remain unchanged.

Currently, Trident (and incidentally Presto) seems to have the correct
behaviour, but Blink, WebKit and Gecko all change window.opener to the
window of the browsing context that has just caused it to navigate.
I believe this to be a very long standing difference (>10 years for Gecko
and Trident)

I am proposing to change Gecko to match the spec, but I was advised to
raise the issue here before going ahead.

Do people agree that window.opener should remain unchanged in this

If agreed, looking at the code, this would seem to be a fairly simple
change for WebKit and Blink as well.


[1] http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#dom-opener

[2] http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name
Received on Monday, 3 March 2014 11:04:31 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:17 UTC