- From: Marcos Caceres <w3c@marcosc.com>
- Date: Tue, 16 Oct 2012 17:55:58 +0100
- To: David Demaree <ddemaree@adobe.com>
- Cc: Matthew Wilcox <mail@matthewwilcox.com>, Tom Lane <tom@tomlane.me>, Peter Gasston <pgasston@gmail.com>, David Newton <david@davidnewton.ca>, François REMY <fremycompany_pub@yahoo.fr>, "public-respimg@w3.org" <public-respimg@w3.org>
On Tuesday, October 16, 2012 at 5:51 PM, David Demaree wrote: > > On Oct 16, 2012, at 10:32 AM, Marcos Caceres <w3c@marcosc.com (mailto:w3c@marcosc.com)> wrote: > > I should stress that while I like <picture>, and have some concerns about @srcset syntax, I absolutely think there's room for both. Absolutely agree! > > @srcset solves the problem of images that are semantically part of the document content, and have a single intrinsic size, but which are available at several levels of resolution/quality, whereas <picture> goes degrees further of both complexity and control. @srcset is probably the wrong solution for changing the dimensions of an image to suit a smaller viewport (i.e., the art direction use case), but it's the right solution for a logo that should be served at quad-resolution for Retina displays with no other special case needs. > > Of course, if another proposal comes along I'm open to anything. I'm not married to any proposal except the idea that this problem ought to be solved. Hat's off. I could not have put it better! This is precisely what I've been trying to say.
Received on Tuesday, 16 October 2012 16:56:26 UTC