[webkit-dev] Limiting slow unload handlers (Re: Back/forward cache for pages with unload handlers)
ojan at chromium.org
Thu Sep 17 14:17:51 PDT 2009
On Thu, Sep 17, 2009 at 2:11 PM, John Abd-El-Malek <jam at google.com> wrote:
> On Thu, Sep 17, 2009 at 2:09 PM, Darin Fisher <darin at chromium.org> wrote:
>> On Thu, Sep 17, 2009 at 12:52 PM, Maciej Stachowiak <mjs at apple.com>wrote:
>>> Based on your comments below, I think the expedient thing to do is to let
>>> Image loads (only) complete their I/O when initiated from unload or
>> Why exclude beforeunload? Some of the sites we found use the busy loop
>> hack in beforeunload.
> These sites presumably did it to split the sleep calls across as many
> handlers as possible to avoid hung script detectors. If they rewrite their
> pages to use one clean method, it seems they only need to do it in one
There a plenty of sites that only have a beforeunload handler and have no
reason to register an unload handler. If you're not prompting the user to
stay on the page, the two events are essentially equivalent.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev