[webkit-dev] Limiting slow unload handlers (Re: Back/forward cache for pages with unload handlers)

John Abd-El-Malek jam at google.com
Fri Oct 16 14:14:17 PDT 2009

I've createdhttps://bugs.webkit.org/show_bug.cgi?id=30457 for the image
https://bugs.webkit.org/show_bug.cgi?id=30458 for <a ping> and

On Thu, Oct 15, 2009 at 3:56 PM, Darin Fisher <darin at chromium.org> wrote:

> On Thu, Oct 15, 2009 at 1:53 PM, Peter Kasting <pkasting at google.com>wrote:
>> On Thu, Oct 15, 2009 at 1:50 PM, John Abd-El-Malek <jam at google.com>wrote:
>>> Does this argue for making the image loading trick work all the time from
>>> JS, not just from unload handlers?  I tested with IE and it looks like the
>>> image trick works all the time, not just in unload handlers.  My test case
>>> was to load the image in the onload handler and change document.location to
>>> "about:blank" right after.  Firefox/Safari/Chrome didn't load the image most
>>> of the time.
>> This would mean normal pages that are still loading would keep loading all
>> their images after navigation, wouldn't it?  Bad.
> Right.  For this reason, limiting it to just unload handlers seems best.
>  It is unlikely that images created during unload would be for anything
> other than pings.

> -Darin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20091016/a8b398d1/attachment.html>

More information about the webkit-dev mailing list