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: Fri, 27 Jan 2012 18:53:15 +0000
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: Cameron McCormack <cam@mcc.id.au>, Allen Wirfs-Brock <allen@wirfs-brock.com>, Ojan Vafai <ojan@chromium.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Ian Hickson <ian@hixie.ch>, Jeff Walden <jwalden@mit.edu>
Message-ID: <9768D477C67135458BF978A45BCF9B3838206888@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
>-----Original Message-----
>From: Boris Zbarsky [mailto:bzbarsky@MIT.EDU]
>Sent: Friday, January 27, 2012 10:44 AM
>To: Travis Leithead
>Cc: Cameron McCormack; Allen Wirfs-Brock; Ojan Vafai; public-script-
>coord@w3.org; Ian Hickson; Jeff Walden
>Subject: Re: variable declarations shadowing named properties on window
>On 1/27/12 7:39 PM, Travis Leithead wrote:
>> So, to clarify my understanding:
>> Name resolution lookup on the window/global will be:
>> 1. window/global own props
>> 2. WindowProperties own props
>> 3. WindowPrototype own props
>> 4. Object [prototype] own props
>> 5. WindowProperties named/indexed props
>I think #2 and #3 are in the opposite order if I understood Cameron

>-----Original Message-----
>From: Cameron McCormack [mailto:cam@mcc.id.au]
>This new object (the "named properties object") behaves like any other
>[NoInterfaceObject] prototype object.  I'll have it stringify to
>"WindowProperties" (analogously to "WindowPrototype" which is what we
>have for Window.prototype now).  It exists just above Window.prototype.

I guess "above" was ambiguous :)

Received on Friday, 27 January 2012 18:53:55 UTC

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