Ian Hickson wrote:
Does:
http://www.whatwg.org/specs/web-apps/current-work/#browsing
...(specifically point 4 in the algorithm)
Quite frankly, I don't see how point 4 is compatible with the real
world. In particular, if point 4 is applied and I create a window with
window.open(), once I've done a single load in it of a page from a
different site I can no longer target that window with loads. That
doesn't seem to be compatible with what UAs do or what sites expect...
...answer your question?
It does answer the question (even modulo my complaint about the
#browsing section).
If so, is the answer acceptable?
I'm not sure. If the answer is accepted, that means that
https://bugzilla.mozilla.org/show_bug.cgi?id=269174 is invalid.
Frankly, that bothers me. In this situation, the window.name set should
really not affect the name of the window for subsequently loaded pages
in the same window... if they come from a different site.
In fact, if I window.open a window and load some page in it, I would
expect the name the opener gave that window to not affect the name the
page sees for it, if the page is from a different site. That's not what
UAs do at all, but what UAs do seems easily attackable to me...
-Boris
