[Bug 5850] JS global object

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5850





--- Comment #15 from Ian 'Hixie' Hickson <ian@hixie.ch>  2008-07-18 08:09:07 ---
So if i have a Window object |window|, and I do:

   var x = window.foo;

...where "foo" is some object or function, and then I navigate |window|, and
then I call x() or access x.bar, does that access the original object's foo? Or
what?

I don't want to specify something that says that "all the references now point
to a different object". That's weird. It's the same object in every sense that
you can check from script. You can't ever get a reference to the underlying
object. So I think it makes more sense to define Window as an object that
forwards everything to an underlying object and just having that object change
as you traverse back and forth.

But then we have:

   (function() { return this })()

...and this breaks down, unless we override ECMA 262 as well, which seems
unwise.

Note to self: When fixing this, I need to go through and deal with references
to things like "the origin of the active document of the browsing context of
the Window object", now that we've split Window.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 18 July 2008 08:09:41 UTC