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

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

From: Charlie Reis <creis@chromium.org>
Date: Thu, 3 Apr 2014 11:28:15 -0700
Message-ID: <CAH+8MBaU3NSq+WvZ2iG8n_-EAaSBZTA_fYOLoMw0NkFpRf4MiA@mail.gmail.com>
To: Bob Owen <bobowencode@gmail.com>
Cc: whatwg@whatwg.org, Ian Hickson <ian@hixie.ch>
On Wed, Apr 2, 2014 at 3:09 PM, Bob Owen <bobowencode@gmail.com> wrote:

> On 2 April 2014 22:00, Ian Hickson <ian@hixie.ch> wrote:
>
> > It's worth noting that there are many many ways to navigate a browsing
> > context beyond window.open(), e.g. <a target="">, window.location,
> > drag-and-drop of a link, window.history.go(), etc.
>
> Absolutely, if we were to converge on the spec for the current opener and
> people felt that last navigator would be useful, then it would need to be
> updated in all cases.
> Although, the history case might hold the original state.
>
> Anyway, getting way ahead of myself.
> I'll see if there are any more opinions, then look to move Gecko towards
> the spec and see if any compat issues arise.
>

For what it's worth, I think we'd be open to changing Blink to match the
spec as well, if you don't find any compat issues.

Charlie
Received on Thursday, 3 April 2014 18:28:42 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:28 UTC