W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2011

[Bug 8241] Named properties on window

From: <bugzilla@jessica.w3.org>
Date: Mon, 20 Jun 2011 03:21:21 +0000
To: public-script-coord@w3.org
Message-Id: <E1QYV3B-0004Sl-Dd@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8241

--- Comment #11 from Boris Zbarsky <bzbarsky@mit.edu> 2011-06-20 03:21:20 UTC ---
In the Firefox, case at least, I think part of your problem is that you're
lumping together _different_ sorts of named properties.  In particular frame
names are treated quite differently from properties that come from the global
scope polluter in Gecko; I can't speak to other browsers.

The exact Gecko name resolution process on Window is:

1)  Something with standard classes (Object, Array, etc).  Not quite sure what
    and how those interact with named frames and the like.
2)  Look for a named frame with that name.
3)  Resolve "_content", "location", "navigator", "document".  Of those,
    "location" and "navigator" are non-configurable, so if you look them up
    before frames with those names are added, you won't be able to override
    them... or something.  I see no particular magic for "document" that would
    obviously explain your results.
4)  "java" and "packages"... I have no idea what that stuff is, except Java is
    involved.
5)  Event handlers.
6)  Properties off the prototype chain.
7)  Global scope polluter.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 20 June 2011 03:21:26 UTC

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