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

Peter Kasting pkasting at google.com
Thu Oct 15 13:53:33 PDT 2009

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.

> I see your points about window.sendPing.  I think it's the most elegant
> solution.  But given that we'll allow the image trick for pragmatic reasons,
> then it's not needed.  Shouldn't the bar for exposing methods be high, i.e.
> only if there's no other way of doing this?

I don't think that should be true at all.  We should expose methods when
they are the best way of doing something.  If you're a new web author and
you want to know how to send some data on command, sendPing is saner and
more likely to show up in your documentation search than an unexpected quirk
of image loading.

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

More information about the webkit-dev mailing list