W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2012

[whatwg] Details on window.open

From: David Bruant <bruant.d@gmail.com>
Date: Sun, 07 Oct 2012 12:32:09 +0200
Message-ID: <50715A29.2080206@gmail.com>
To: whatwg <whatwg@whatwg.org>

I've been searching on the web for complete documentation about
window.open and I have some unanswered questions.
1) what are the rules for popup blockers? Is every call to window.open
blocked in modern browsers or are there exceptions?

2) About the third argument, is there a somewhat interoperable overlap
in implementations or is it just an intricable mess?

3) Is what is returned a instance of Window or WindowProxy? By that I
mean that if one browsing context A opens C and B window.open C too
changing the URL (and reloading), is A supposed to have access to the
new C or only the old browsing context?

4) About step 4 of The rules for choosing a browsing context given a
browsing context name [1]:
> If the given browsing context name is not |_blank| and there exists a
> browsing context whose name
> <http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#browsing-context-name>
> is the same as the given browsing context name, and the current
> browsing context is allowed to navigate
> <http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#allowed-to-navigate>
> that browsing context, and the user agent determines that the two
> browsing contexts are related enough that it is ok if they reach each
> other,
What does "related enough" mean?
How is it implemented in different browsers?

> then that browsing context must be the chosen one. If there are
> multiple matching browsing contexts, the user agent should select one
> in some arbitrary consistent manner, such as the most recently opened,
> most recently focused, or more closely related.
What is the "consistent manner" in each implementation?


Received on Sunday, 7 October 2012 10:32:51 UTC

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