- From: David Newton <david@davidnewton.ca>
- Date: Mon, 15 Oct 2012 13:09:28 -0400
- To: François REMY <fremycompany_pub@yahoo.fr>
- Cc: "Marcos Caceres" <w3c@marcosc.com>, <public-respimg@w3.org>
Received on Tuesday, 16 October 2012 07:06:44 UTC
On 2012-10-15, at 12:52 PM, François REMY <fremycompany_pub@yahoo.fr> wrote: > | <picture> > | <source type="image/webp" srcset="small.wp, medium.wp 2x, big.wp 3x"> > | <source srcset="small.gif, medium.png, big.jpg"> > | </picture> > > This is what I had in mind indeed; you don't need to define the possible values for the 'type' attribute: you can just say it should be a valid mime type. > > After that, it's up to browsers to define which mime types they support and which one they don't. > Yes, this is exactly what I was thinking too. In terms of what's out there now, I did some really quick searching and found some stuff. WebP in use: Torbit using WebP: http://torbit.com/blog/2011/04/05/torbit-adds-support-for-webp/ and http://torbit.com/blog/2011/05/02/webp-statistics/ Opera Turbo proxy using WebP: http://googlesystem.blogspot.ca/2011/04/opera-turbo-uses-webp-to-compress.html Polyfills etc: server-side browser detect to serve WebP-specific CSS to Chrome/Opera: http://code.anjanesh.net/2011/04/using-webp-image-format-for-browsers.html JS solutions to load WebP when it's supported: http://nnucomputerwhiz.com/use-webp-images-with-jpeg-fallback.html and http://stackoverflow.com/questions/5573096/detecting-webp-support
Received on Tuesday, 16 October 2012 07:06:44 UTC