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

[whatwg] keepalive attribute on iframe

From: Ojan Vafai <ojan@chromium.org>
Date: Thu, 12 Apr 2012 12:41:15 -0700
Message-ID: <CANMdWTtc6YF3Skw6+YZTOJR45AkYFWiu_MaC9m0ZoWYLKAbdYg@mail.gmail.com>
I thought the issue here was with moving iframes across documents, not with
keeping disconnected iframes alive. I'll ping the engineers working on this
and see if I can get more information.

On Thu, Apr 12, 2012 at 12:37 PM, Adam Barth <w3c at adambarth.com> wrote:

> We just got finished removing this feature from WebKit because it
> caused many security and stability problems.  It turns out that
> there's a lot of code in browsers that can't cope with a disconnected
> iframe being alive.
>
> Adam
>
>
> 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 Thursday, 12 April 2012 12:41:15 GMT

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