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

Re: srcN - Alternative to picture and srcset

From: Aaron Gustafson <aaron@easy-designs.net>
Date: Sun, 3 Nov 2013 14:03:23 -0500
Message-ID: <CALWPYzExYkfef8w4Vg6O0S6CbJ=06xr24U4GeBVJgpTo-L-v0Q@mail.gmail.com>
To: "Podjarny, Guy" <gpodjarn@akamai.com>
Cc: Attiks <attiks@gmail.com>, Anselm Hannemann <info@anselm-hannemann.com>, Yoav Weiss <yoav@yoav.ws>, Marcos Caceres <marcos@marcosc.com>, "matmarquis.com" <mat@matmarquis.com>, François REMY <francois.remy.dev@outlook.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, Shane Hudson <shane@shanehudson.net>, "public-respimg@w3.org" <public-respimg@w3.org>, Robin Berjon <robin@w3.org>
On Sun, Nov 3, 2013 at 1:48 PM, Podjarny, Guy <gpodjarn@akamai.com> wrote:

> I didn't think this through fully yet, but isn't this only a problem if we
> change the contents of the picture (e.g. Art direction) as opposed to
> reducing quality or pixel density?
>


Correct. It’s only an issue if you have multiple layouts.



> If so, we could just declare that srcN doesn't support multiple usemap
> options, meaning you can only (successfully) use it if you're limiting your
> use of srcN to viewport and DPR switching.
> Makes sense?
>


Completely. I would be in favor of this restriction as the alternative
makes me cringe.

Cheers,

Aaron

----
Aaron Gustafson
Founder & Technical Lead
Easy Designs, LLC
@aarongustafson
Received on Sunday, 3 November 2013 19:04:10 UTC

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