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: Boris Zbarsky <bzbarsky@mit.edu>
Date: Wed, 14 Jan 2015 21:04:33 -0500
Message-ID: <54B72031.80108@mit.edu>
To: Travis Leithead <travis.leithead@microsoft.com>, "Mark S. Miller" <erights@google.com>
CC: es-discuss <es-discuss@mozilla.org>, Domenic Denicola <domenic@domenicdenicola.com>, Ian Hickson <ian@hixie.ch>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On 1/14/15 8:49 PM, Travis Leithead wrote:
> and existing elements and their document are disconnected from the
> window, while a new document and the new elements created from parsing
> are put in their place.

More precisely, the old elements are disconnected from the document, the 
document is disconnected from the window, and the document is connected 
to the new window.

> Implementations differ on how they handle the scenario. Boris notes that
> Gecko just creates a new window (with a new document, etc.)

No, it's the same document.

> Boris can correct me if I got this wrong.

You got it wrong.  ;)

Received on Thursday, 15 January 2015 02:05:03 UTC

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