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

RE: variable declarations shadowing named properties on window

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Wed, 4 Jan 2012 18:21:58 +0000
To: Boris Zbarsky <bzbarsky@MIT.EDU>, Ojan Vafai <ojan@chromium.org>
CC: Cameron McCormack <cam@mcc.id.au>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Allen Wirfs-Brock <allen@wirfs-brock.com>, Ian Hickson <ian@hixie.ch>
Message-ID: <9768D477C67135458BF978A45BCF9B38381E5E1E@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
>-----Original Message-----
>From: Boris Zbarsky [mailto:bzbarsky@MIT.EDU]
>On 1/4/12 3:24 AM, Ojan Vafai wrote:
>> IE and Opera already do this and have done so for a long time, right?
>They've allowed var to shadow the frame names, right?
>Have they actually put the frame names somewhere on the proto chain
>other than the global itself?  Doing that changes behaviors other than
>that of var....

The described behavior has been in IE for a while. In Trident, frame references are just another global scope polluter, but with higher priority. The var declarations are assigned the undefined value (I believe), and so they shadow everything else in the lookup order.
Received on Wednesday, 4 January 2012 18:22:34 UTC

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