Re: Global variables and id lookup for elements

On Wed, 20 Jul 2011, Cameron McCormack wrote:
> Ian Hickson:
> > Is this still something I should do, or did this get resolved using 
> > another solution?
> The proposed solution I made in the bug was to have the [[Get]] etc. 
> internal methods of Window handle the resolution order of window named 
> properties, rather than to use inheritance in the IDL to control the 
> order.  I made that change to Web IDL, which would require you defining 
> which named properties are “resolved before prototype properties”, 
> and that’d be the frame names; the (possible quirks mode only) ID 
> lookups would be done last automatically, since Window isn’t 
> [OverrideBuiltins].
> However, Tony Ross on the bug there says he would rather an even simpler 
> solution that resoles all frame names and ID lookups after everything 
> else (i.e. like normal non-[OverrideBuiltins] interfaces).  I haven’t 
> made any spec changes since then.  It would be good to get more input on 
> the bug.

Ok, thanks.

I have no opinion on what exactly we should do here. Since it's assigned 
to you, I'll let you make the call; if any changes should be necessary in 
the HTML spec (e.g. removing the [ReplaceableNamedProperties] annotation 
or changing the prose for the getter) please describe the needed change 
and reassign the bug to me (in an open state).


Ian Hickson               U+1047E                )\._.,--....,'``.    fL       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Received on Wednesday, 20 July 2011 00:25:08 UTC