W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2012

Re: [whatwg] <img srcset> for responsive bitmapped content images

From: Edward O'Connor <eoconnor@apple.com>
Date: Thu, 10 May 2012 04:44:25 -0700
Message-id: <F1C77042-7EF2-443C-8605-4AE973A7D29F@apple.com>
To: whatwg@whatwg.org
Aryeh wrote:

> I'd like to throw in another use-case that might be addressable by the
> same feature: allowing "Save As..." to save a different version of the
> image (e.g., higher-res) than is actually displayed.
[…]
> Another obvious use-case I'd like to point out is print.

Yes, these are both excellent reasons for us to adopt such a feature,
and the <img srcset> proposal can handle both cases.

> A fourth use-case I'd like to suggest is vector images. Last I
> checked, many authors don't want to serve SVG directly because too
> many browsers don't support it in <img> (or at all).

I'm not sure about this one. If a browser doesn't support SVG, I want to
be able to provide a bitmap fallback regardless of how I included the
SVG—in both the <img src> or inline <svg> element cases. <img srcset>
isn't about providing fallback, so this might best be addressed with a
different feature.

> It's possible that the best solution won't accommodate all of these
> use-cases, but I'm just throwing them out here so that they can be
> taken into account.

*nod*


Thanks,
Ted
Received on Thursday, 10 May 2012 11:47:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:08 GMT