This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Web IDL in bug 8241 has just introduced a term "resolve before prototype properties", which can be used to describe named properties that need to be resolved after looking at the own object but before the prototype chain. This is needed for Window's property resolution behaviour, which as bug 8241 points at, in most browsers requires looking for frame names earlier than global scope polluter properties. I suggest in the second list item after "The Window interface supports named properties." say that these named properties are "resolved before prototype properties", and link to #dfn-resolved-before-prototype-properties in the Web IDL spec.
mass-move component to LC1
I've removed that term now, to simplify named properties on window. HTML will need to state that the frame properties are resolved in preference to the global scope polluter properties.
heycam: Does WebIDL define "global scope polluter properties"? I couldn't find it. I'm not really sure what you want the HTML spec to say here.
(In reply to comment #3) > heycam: Does WebIDL define "global scope polluter properties"? I couldn't find > it. No, but by that I (and others I think) were just referring to the non-frame named properties on Window. > I'm not really sure what you want the HTML spec to say here. I think the HTML spec then is fine and doesn't need to change, since the algorithm at http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#dom-window-nameditem already resolves frames before named elements.
Excellent! In that case: EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: no spec change Rationale: This seems to have been fixed already.