19490 2012-10-11 22:47:57 +0000 srcset proposal is not fully responsive 2014-01-31 18:47:29 +0000 1 1 1 Unclassified HTML WG The srcset attribute unspecified PC All CLOSED FIXED P2 normal --- 23243 1 eoconnor eoconnor david marcosscaceres w3c zcorpan public-html-bugzilla oldest_to_newest 76053 0 eoconnor 2012-10-11 22:47:57 +0000 Marcos wrote: > In section "Processing the image candidates", the srcset spec [1] says: > > "The user agent may at any time run the following algorithm to update an > img element's image in order to react to changes in the environment. > (User agents are not required to ever run this algorithm.)" > > The RICG is wondering why this is not at least a SHOULD or a MUST? Most > developers would expect this to work like media queries (i.e., always > "responsive" to environmental changes). > > Some clarification would be great. 76054 1 eoconnor 2012-10-11 22:48:30 +0000 Originally filed on public-html-comments: http://lists.w3.org/Archives/Public/public-html-comments/2012Oct/0002.html 76460 2 eoconnor 2012-10-16 22:30:27 +0000 There are several scenarios that come to mind in which a User Agent may reasonably wish not to re-invoke this algorithm. For instance, consider the case of a UA which goes offline after the page has loaded. If it had to re-invoke this algorithm when something happens while the UA is offline, the image may go from a working state to a broken state. Do you think the spec needs to be updated to clarify this in some non-normative prose, or is the above sufficient to answer your question? 77038 3 w3c 2012-10-24 12:11:59 +0000 That makes sense. I think it would be helpful to outline such scenarios as a note in the spec. 93654 4 eoconnor 2013-09-23 16:29:24 +0000 Reopening to ensure I merge over whatever notes get added via bug 23243. 93661 5 zcorpan 2013-09-23 17:43:10 +0000 (In reply to Edward O'Connor from comment #2) > If it had to > re-invoke this algorithm when something happens while the UA is offline, the > image may go from a working state to a broken state. No, if the fetch fails, the old image is kept. "If this download fails in any way (other than the response code not being a 2xx code, as mentioned earlier), or if the image format is unsupported (as determined by applying the image sniffing rules, again as mentioned earlier), or if the resource type is multipart/x-mixed-replace, then abort these steps." 99442 6 eoconnor 2014-01-29 22:59:44 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: https://github.com/w3c/html/commit/ebc9908575f457701d8a8359123261995c20ac41 Rationale: Merged fix from WHATWG.