W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2012

Re: "var" declarations shadowing properties from Window.prototype

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Sun, 12 Aug 2012 19:24:05 -0400
Message-ID: <50283B15.2020109@mit.edu>
To: Brendan Eich <brendan@mozilla.com>
CC: Brandon Benvie <brandon@brandonbenvie.com>, public-script-coord@w3.org, es-discuss@mozilla.org
On 8/12/12 5:29 PM, Brendan Eich wrote:
> Boris Zbarsky wrote:
>> Note that data in
>> http://lists.w3.org/Archives/Public/public-script-coord/2012JanMar/0033.html
>> suggests that IE also implements the erratum to 5.1 we were talking
>> about up-thread.  Oh what a tangled web we weave.
> Yes, current thinking is that we should take the erratum that major JS
> engines already fixed, and include it in ES6. But this means we must do
> something different in WebIDL, probably make own global properties for
> window-implements-interface-inherited attributes and even operations.
> And then (for strict mode) be careful about get-only accessors. This
> reminds me of [Replaceable], which was for non-writable but configurable
> data properties that var and function must be able to replace. It's kind
> of the opposite and only for accessors:
> var-captures-own-accessor-via-detection, or some such.
> Just recapping, tell me if I'm missing something.

The above sounds like a reasonable summary to me.  Certainly hits all 
the high points of the discussion, with the addition that the GSP as 
currently specced depends on the erratum sticking around.

Received on Sunday, 12 August 2012 23:24:38 UTC

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