W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2015

Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 15 Jan 2015 18:59:18 +0000 (UTC)
To: Boris Zbarsky <bzbarsky@mit.edu>
cc: Yehuda Katz <wycats@gmail.com>, Filip Pizlo <fpizlo@apple.com>, "Mark S. Miller" <erights@google.com>, es-discuss <es-discuss@mozilla.org>, Domenic Denicola <domenic@domenicdenicola.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Travis Leithead <travis.leithead@microsoft.com>
Message-ID: <alpine.DEB.2.00.1501151857450.6653@ps20323.dreamhostps.com>
On Thu, 15 Jan 2015, Boris Zbarsky wrote:
> > 
> > It doesn't match _all_ implementations, certainly.
> OK, but have you bothered to find out why?

The usual reason is just that there was no spec initially, and that the 
relevant implementations haven't bothered to fix it since the spec was 

> > Per the HTML spec, there's two ways that WindowProxy can change. One 
> > is session history traversal. That can never happen with JS on the 
> > stack
> Are you sure, given showModalDialog?

I'm assuming that showModalDialog() is dead. showModalDialog() breaks 
every assumption under the sun and is generally bad news.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 15 January 2015 18:59:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC