[Bug 5850] JS global object

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





--- Comment #21 from Ian 'Hixie' Hickson <ian@hixie.ch>  2008-07-23 11:14:07 ---
Opera is doing something weird with multiple Window objects where other UAs
just have one. q.v.:
   http://damowmow.com/playground/demos/global-object/008.html

IE won't let you access code in pages that are no longer the frame's active
document:
   http://damowmow.com/playground/demos/global-object/010.html

For properties on the global object that are defined in the IDL:
   http://damowmow.com/playground/demos/global-object/009.html
Both Safari and Firefox seem to refer to the properties for the most active
document, even for the scope chain, if using a nested browsing context. If we
use a separate window, as in:
   http://crypto.stanford.edu/~abarth/research/html5/split/test03.html
...then things on the scope chain refer to the old objects, except the window
property returns the window object which has been updated to point to the new
objects.

For properties on the global object that aren't IDL-defined properties:
   http://damowmow.com/playground/demos/global-object/004.html
Safari does the thing where the Window object acts like a proxy to the global
object at the top of the scope chain, so things stay in scope but can't be seen
from old or new references to 'this' or 'window'. If it's a nested browsing
contex,t then Firefox clears out the global object, much like the spec says to
today, but if it's a top-level browsing context, then it does what Safari does
(c.f. test03 above).


-- 
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 Wednesday, 23 July 2008 11:14:42 UTC