You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Create reusable image fetching logic for other standards #4474
Ported from https://www.w3.org/Bugs/Public/show_bug.cgi?id=24055. Standards like Notifications or Web App Manifest need to fetch images. It's unclear which portions of <img>'s very-complicated processing model they should involve, but in that bug people seem to be advocating for at least MIME sniffing and the "list of available images" cache.
This also impacts <input type="image">, and probably <link rel="icon">.
The thread is long and someone planning to tackle this should probably read through it and distill it here before going too far.
Note: #1643 is probably a prerequisite for this issue.
zcorpan: old issue. Browsers are probably reusing image loading logic for many things, but HTML Standard only specifies special logic for <img>. This makes adding new image-loading features, e.g. to CSS, hard. No work in the last 7 years to my knowledge. Any progress on solving this, or new information on how to solve?
emilio: interop issues with CSS images having different caching policies. But usually all browsers have a centralized image loader. Shared caches, and so on.
zcorpan: also an issue with the image cache. Probably doesn't match implementations.
emilio: changed Gecko to match spec a bit better for image cache. This can also affect preloading.
Domenic: interest from chromium to work on memory cache, image cache..
emilio: arch in gecko is different from chromium. if you have an uncachable image loaded from a stylesheet, (something something)
Domenic: interop issue is important. emilio you seem to have knowledge about this
emilio: happy to work on this
<annevk> And with EXIF there’s decoding considerations too that need centralization (And I guess in general we want uniform image decoders across features that consume images.)
Domenic: I'll take the action item to start the discussion to collate the concrete interop issues.
Activity
annevk commentedon Feb 4, 2020
This is also needed for CSS
background-imageet al. All fetching of images should share the same pipeline.annevk commentedon Oct 26, 2020
See also w3c/csswg-drafts#5173 and various issues linked from there.
zcorpan commentedon Oct 29, 2020
This was discussed a few days ago in the WHATWG TPAC breakout session. Minutes at https://www.w3.org/2020/10/26-whatwg-minutes.html#fetching (cc @emilio )