20175 2012-11-30 15:19:18 +0000 Lacks means to sensibly manipulate sources 2013-01-29 20:13:54 +0000 1 1 1 Unclassified HTML WG The srcset attribute unspecified PC All RESOLVED NEEDSINFO P2 normal --- 20211 20255 1 w3c eoconnor bkardell david mat odinho public-html-bugzilla oldest_to_newest 79182 0 w3c 2012-11-30 15:19:18 +0000 The img@srcset solution lacks a means to programmatically interface with image resources, as well as access relevant attributes and methods that make the solution practical to work with (i.e., it shouldn't require Regex or nested loops to manipulate values). See: https://gist.github.com/9f3ced6a91d7390b080d 82305 1 eoconnor 2013-01-29 19:25:12 +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: Additional Information Needed Change Description: No spec change. Rationale: The linked gist certainly demonstrates that manipulating srcset="" from JS can be awkward. I think adding a DOMTokenList-like API to srcset="" would be reasonable if we had use cases which required frequent manipulation of srcset="" from JS. So, to echo Ian's question in bug 20211 comment 1, what's the use case here?