This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/edits.html Multipage: http://www.whatwg.org/C#img-load Complete: http://www.whatwg.org/c#img-load Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html Comment: <img> "list of available images" and HTTP cache semantics The "list of available images" seems to always be used even the resource doesn't allow caching according to HTTP. I guess the spec allows items in the cache to be removed at any time, so a UA could choose to remove items according to HTTP cache semantics, but it would be better to be explicit if that's what we want to happen. Posted from: 210.95.255.149 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 OPR/21.0.1432.48 (Edition Next)
What do browsers do? I would imagine they ignore HTTP caching headers entirely here.
Specify how 'list of available images' and HTTP cache interact. https://github.com/ResponsiveImagesCG/picture-element/commit/22efd4478d7714ac12fd128ca2c455d0f91f42a4