Should images other than img use the list of available images?

[npm1]

Currently, the list of available images is only referenced from HTMLImageElement processing model, would it make sense to unify with SVGImageElement and HTMLVideoElement's poster image?

[domenic]

My understanding is that the "list of available images" corresponds to what browsers today call the "memory cache", or something like that. So yeah, it's probably pretty generally applicable, indeed beyond just images. @yoavweiss @domfarolino as folks who should know more, including where we are on standardizing the memory cache.

[yoavweiss]

Yeah, the "list of available images" is the closest thing we got to the memory cache implemented in Blink and WebKit.
We should be standardizing the whole thing (or its subset that is the "preload cache"), but it hasn't been on the top of anyone's TODO list AFAIK.

Maybe a good first step would be to unify image loading to go through this single algorithm (or move the list of available images further down the stack and into Fetch).

[annevk]

Duplicating this into #4474.