[Webkit-unassigned] [Bug 248025] Dynamically added loading="lazy" image when already is not reusing the cached image when available

[bugzilla-daemon at webkit.org]

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

--- Comment #3 from Karl Dubost <karlcow at apple.com> ---
ha interesting in 
https://html.spec.whatwg.org/multipage/images.html#the-list-of-available-images


> 4.8.4.3.3 The list of available images
> 
> Each Document object must have a list of available images. Each image in this list is identified by a tuple consisting of an absolute URL, a CORS settings attribute mode, and, if the mode is not No CORS, an origin. 


There is a note:

> The list of available images is intended to enable synchronous switching when changing the src attribute to a URL that has previously been loaded, and to avoid re-downloading images in the same document even when they don't allow caching per HTTP. It is not used to avoid re-downloading the same image while the previous image is still loading.


And in https://html.spec.whatwg.org/multipage/images.html#updating-the-image-data

Step 6.3

> If the list of available images contains an entry for key, then:
> 
> * Set the ignore higher-layer caching flag for that entry.
> 



And this is a similar test case
http://wpt.live/html/semantics/embedded-content/the-img-element/image-loading-lazy-use-list-of-available-images.html
https://wpt.fyi/results/html/semantics/embedded-content/the-img-element/image-loading-lazy-use-list-of-available-images.html

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20221121/fed2021b/attachment.htm>