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

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

From: Ryosuke Niwa <rniwa@apple.com>
Date: Tue, 01 Jul 2014 19:18:03 -0700
Message-id: <8D45BAE2-9AA0-4875-9D19-236EE5684C87@apple.com>
To: Bob Owen <bobowencode@gmail.com>
Cc: whatwg@whatwg.org
Could you point me to a specific test case that demonstrates the difference?

On Mar 3, 2014, at 3:04 AM, Bob Owen <bobowencode@gmail.com> wrote:

> Hi,
> 
> 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
> circumstance?
> 
> If agreed, looking at the code, this would seem to be a fairly simple
> change for WebKit and Blink as well.
> 
> Thanks,
> Bob
> 
> [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 Wednesday, 2 July 2014 02:18:41 UTC

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