[Webkit-unassigned] [Bug 76102] Add support for loadstart, progress, and loadend ProgressEvents to the IMG tag.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon May 4 04:22:52 PDT 2015


https://bugs.webkit.org/show_bug.cgi?id=76102

--- Comment #15 from Simon Pieters <zcorpan at gmail.com> ---
(In reply to comment #14)
> Yes it is part of the WHATWG HTML Living Standard specs. Search for
> "loadstart" in
> http://www.whatwg.org/specs/web-apps/current-work/#the-img-element.

That algorithm is not run "eg. on orientation change". Then this algorithm is run instead https://html.spec.whatwg.org/multipage/embedded-content.html#img-environment-changes and it does not fire loadstart/progress.

> I think there is no other way of detecting that a (specific) image starts
> being loaded by the browser. That can be useful for displaying loading
> indications.

Why would you want a loading indicator for environment changes instead of just swapping the image when it is loaded?

> I find it especially interesting when using the <picture> element. By using
> <picture>, the src of an <img> tag can change after the page finished
> loading, eg. on a viewport resize or an orientation change. That results in
> a blank/white image for the time the images is actually being loaded - with
> a loadstart event you could let the user know about the loading, eg. by
> showing a loading indicator.

No, the old image would keep showing until the new one is completely loaded, per spec.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150504/771a1685/attachment-0001.html>


More information about the webkit-unassigned mailing list