- From: Adam Barth <w3c@adambarth.com>
- Date: Thu, 26 Aug 2010 23:06:30 -0700
On Thu, Aug 26, 2010 at 12:27 AM, Boris Zbarsky <bzbarsky at mit.edu> wrote: > On 8/26/10 3:23 AM, James May wrote: >> Couldn't the iframe be kept alive, but remain "associated" with it's >> parent browsing context until (if) it was re-parented / inserted into a >> different document. (does this match what other elements in the DOM >> behave in terms of event handlers when they are detached?) > > Elements behave fine. ?The question is what the Window should do. ?What > should window.parent return in the iframe while detached? ?window.top? What > should window.resizeTo do? ?That sort of thing. Something like this is shipping in various WebKit-based browsers. You can experiment to see at least one take on how to answer these questions. I agree that it's a kind of dark corner of the state machine and therefore risky, both in terms of stability and security. Adam
Received on Thursday, 26 August 2010 23:06:30 UTC