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

Re: variable declarations shadowing named properties on window

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 05 Jan 2012 22:18:50 -0500
Message-ID: <4F06681A.6090002@mit.edu>
To: Cameron McCormack <cam@mcc.id.au>
CC: Allen Wirfs-Brock <allen@wirfs-brock.com>, Ojan Vafai <ojan@chromium.org>, Travis Leithead <travis.leithead@microsoft.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Ian Hickson <ian@hixie.ch>, Jeff Walden <jwalden@mit.edu>
On 1/5/12 10:08 PM, Cameron McCormack wrote:
> Only if we want to keep them on window. If we're happy to move them to
> the prototype then we're safe, I believe.

Indeed.

> They can for window.foo but not for bareword lookups. window.foo will do
> a [[Get]], and we could have that return the frame while
> [[GetOwnProperty]] returns undefined. That breaks barewords, though,
> which definitely do use HasBinding and so [[GetOwnProperty]] to
> determine if the reference can be resolved or not.

OK, it sounds like moving this stuff to some proto of the window is the 
way to go, unless we make some more ES spec changes of some sort.

I'm perfectly happy with that, so someone else (who really wants to keep 
the GSP and whatnot on the window) would need to figure out what those 
changes should be and argue for them if they want them to happen.... ;)

-Boris
Received on Friday, 6 January 2012 03:19:23 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:05 UTC