W3C home > Mailing lists > Public > public-respimg@w3.org > October 2013

Re: srcN - Alternative to picture and srcset

From: Marcos Caceres <marcos@marcosc.com>
Date: Mon, 7 Oct 2013 15:26:58 +0100
To: François REMY <francois.remy.dev@outlook.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Shane Hudson <shane@shanehudson.net>, "public-respimg@w3.org" <public-respimg@w3.org>, Robin Berjon <robin@w3.org>
Message-ID: <BF3340B600314BB3A35E1FC6334F2494@marcosc.com>

On Friday, September 27, 2013 at 6:59 PM, François REMY wrote:

> Not saying this is the way to go, but I don't like the srcN part of the proposal either. It's not really script friendly either because you can't read or update them all at the same time.  
It would be a bit of a nightmare to try to update the single attribute version without having a specific API to split everything into its component parts (if one tries to update this "by hand", doing anything wrong would invalidate the whole attribute - as the spec provides no error recovery). At least the multiple attribute version is a bit easier to work with, though it's fairly hard to reason about.  

Regardless, there doesn't appear to be a lot of use cases for updating the attribute dynamically or for getting any kind of event (apart from what you already get with <img>). Those could be added down the line as needed… right now, src-n seems like a suitable evolutionary step that meets the "80% use cases" criteria.  

Marcos Caceres
Received on Monday, 7 October 2013 14:27:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:06:10 UTC