Re: should window.foo return a HTMLCollection if div id=foo and form name=foo exist?

On 11/15/12 6:29 AM, Martin Honnen wrote:
> So two questions, why is "window.foo" first undefined and suddenly
> defined after an access to "foo"?

Because we used to only do global scope pollution on unqualified 
lookups.  I suggest retesting in a nightly build.

> And shouldn't "window.foo" as well as "foo" not return a HTMLCollection?

At the moment, our gsp implementation does the bare minimum needed for 
web compat (given that we only recently gave up on trying to get this 
removed from the spec in the first place).  If someone wants to make it 
more complicated to match the spec here, I'm happy to review the patch, 
but otherwise it's a low priority, since this entire "feature" is 
completely broken by design and bad for the web to start with....

-Boris