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

Re: srcN - Alternative to picture and srcset

From: Scott Jehl <scottjehl@gmail.com>
Date: Fri, 27 Sep 2013 06:57:04 -0500
Message-Id: <C14D62D2-3583-474F-9AB6-1E9BA4056FBF@gmail.com>
Cc: "public-respimg@w3.org" <public-respimg@w3.org>, "Tab Atkins Jr." <jackalmage@gmail.com>, Robin Berjon <robin@w3.org>
To: Marcos Caceres <marcos@marcosc.com>
Thanks Tab

A few questions:


> Their most popular attempt so far, the <picture>element, only hits 2 of the 3 major use-cases, and has certain aspects that implementors seem to be rather unhappy with.

Just to clarify,which major use case does picture (or picture with srcset ) not address?

2: this proposed syntax uses src to reference a large image fallback for non-srcN browsers, but it seems more common today to start with a small image in src and override upward with media queries - is that possible with srcN too?

3. In non-supporting browsers, the src image always will be http prefetched,meaning a polyfill for this syntax may not be able to avoid wasteful overhead. Element based approaches like picture can avoid overhead through use of noscript wrappers on fallback content.  Could srcN be polyfilled without waste?

Scott Jehl

> On Sep 27, 2013, at 5:20 AM, Marcos Caceres <marcos@marcosc.com> wrote:
> Hi All,
> Tab Atkins has put forward and alternative proposal to both srcset and picture:
> http://tabatkins.github.io/specs/respimg/Overview.html
> It combines what was originally in <source> and `srcset` into a "srcN" attribute. Example: 
>  <img src1="(max-width: 400px) pic-small.jpg"
>       src2="(max-width: 1000px) pic-medium.jpg"
>       src="pic-large.jpg"
>       alt="Obama talking to a soldier in hospital scrubs."> 
> Please take a look and discuss. I've cc'ed Tab who I'm sure can answer any questions. 
> Kind regards,
> Marcos 
> -- 
> Marcos Caceres
Received on Friday, 27 September 2013 12:28:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:12:40 UTC