25890 2014-05-27 06:46:12 +0000 <img> Environment change case aborts if a load is in progress 2015-09-16 12:44:12 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#img-determine-type P3 normal Unsorted 1 contributor zcorpan ian mike zcorpan oldest_to_newest 106820 0 contributor 2014-05-27 06:46:12 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/edits.html Multipage: http://www.whatwg.org/C#img-determine-type Complete: http://www.whatwg.org/c#img-determine-type Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: <img> Environment change case aborts if a load is in progress Step 2 says "⌛ If the img element ... is not in the completely available state, ... or if its update the image data algorithm is running, then abort this algorithm." Do we want that? Should the UA run the algorithm again when the pending load has completed? Since <img src> is able to load two resources at the same time, possibly we should be doing that here also so that the new image gets downloaded sooner. Posted from: 90.230.218.37 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.86 Safari/537.36 OPR/22.0.1471.16 (Edition Next) 106953 1 ian 2014-05-28 22:20:25 +0000 The idea is to avoid thrashing, e.g. if you have a size for 100px, 200px, 300px, 400px, and 500px, and the user is wiggling the window width around, it's better to actually get one of them down and render it than it is to keep canceling a load and switching to another and then switching back and so on and never actually getting a complete image. But yeah, this could be updated to use the parallel loading stuff. 113179 2 zcorpan 2014-10-15 08:40:59 +0000 https://github.com/ResponsiveImagesCG/picture-element/commit/c798686911c2bf9334899ac44e0e4a11fa000b19