[Bug 5850] JS global object

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


Adam Barth <w3c@adambarth.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |w3c@adambarth.com




--- Comment #2 from Adam Barth <w3c@adambarth.com>  2008-07-10 07:30:24 ---
Are you planning to spec what happens when a frame holds on to objects from a
frame and then navigates that frame to another location?  Things get
complicated in that case.  For example, you start to see split windows:

http://wiki.mozilla.org/Gecko:SplitWindow
https://bugzilla.mozilla.org/show_bug.cgi?id=296639

The issue here is that pointers to contentWindows (say obtained via
window.frames[0]) persist across navigations (meaning they refer to the new
contents of a frame after the frame has been navigated), but objects inside the
navigated frame can't have their global object switched upon navigation
(otherwise their prototypes and scope chains will be confused, i.e.
exploitable).


-- 
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 Thursday, 10 July 2008 07:31:07 UTC