W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2012

[whatwg] keepalive attribute on iframe

From: Erik Arvidsson <arv@chromium.org>
Date: Mon, 16 Apr 2012 17:00:32 -0700
Message-ID: <CAJ8+GoiXXookanMN0G+=civbs8DbBARWyT=1SSPT-eO=Te+DFA@mail.gmail.com>
FWIW, IE used to not reload iframes when they were moved around in the
tree. They changed this behavior in IE9 so maybe there was some compat
issues?

erik







On Mon, Apr 16, 2012 at 16:51, Darin Fisher <darin at chromium.org> wrote:
> Can you hide this behind adoptNode just as we did for "magic iframe"? ?The
> nice thing about adoptNode is that the browser gets told both the source and
> destination parent nodes. ?This way there is never a disconnected state.
>
> So long as we unload when moving between documents, we should be pretty
> safe as far as the issues which plagued magic iframe are concerned.
>
> -Darin
>
>
> On Thu, Apr 12, 2012 at 12:35 PM, Ojan Vafai <ojan at chromium.org> wrote:
>
>> We should add a keepalive attribute to iframes that prevents iframes from
>> being unloaded/reloaded when removed from or appended to a document.
>> Similarly, a disconnected iframe with keepalive should load. If the
>> keepalive attribute is removed from a disconnected iframe, then it should
>> unload.
>>
>> I'm not terribly happy with the name 'keepalive', but I can't think of
>> anything better at the moment.
>>
>> As iframes increasingly become the standard way of achieving certain tasks
>> (e.g. sandboxing), it's increasingly important to be able to move them
>> around in the DOM. Right now, to achieve this sort of keepalive behavior,
>> you have to keep the iframe always appended to the document and position it
>> absolutely as the document changes.
>>
>> Ojan
>>
Received on Monday, 16 April 2012 17:00:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:07 GMT