W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2010

[whatwg] Should events be paused on detached iframes?

From: Dirk Pranke <dpranke@chromium.org>
Date: Tue, 24 Aug 2010 16:11:02 -0700
Message-ID: <AANLkTinf-d3aiJVP=-j8iZ8hLr9AGAqCvADrNtaf+QG0@mail.gmail.com>
On Tue, Aug 24, 2010 at 3:59 PM, Dmitry Titov <dimich at chromium.org> wrote:
> At least spec tells that if an iframe is detached from the DOM and then
> becomes eligible for GC (not hold via JS reference not DOM connection) - it
> gets unloaded w/o onunload firing (4.8.2):
> On the other hand, if an iframe is removed from a Document and is then
> subsequently garbage collected, this will likely mean (in the absence of
> other references) that the child browsing context's WindowProxy object will
> become eligble for garbage collection, which will then lead to thatbrowsing
> context being discarded, which will then lead to its Document being
> discarded also. This happens without notice to any scripts running in that
> Document; for example, no unload events are fired (the "unload a document"
> steps are not run).
> Seems there are bugs to fix :-)
>

Well, perhaps, but on the other hand given that the spec doesn't match
*any* current browser, I'm not sure that it's what we really want to
have happen. I defer to wiser heads than myself on this issue.

-- Dirk
Received on Tuesday, 24 August 2010 16:11:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:00 UTC