[webkit-dev] The SrcN responsive images proposal

Maciej Stachowiak mjs at apple.com
Fri Nov 8 12:25:09 PST 2013

On Nov 8, 2013, at 9:06 AM, John Mellor <johnme at chromium.org> wrote:

> Most discussion so far seems to be bikeshedding the syntax. To make this more productive, can we focus on the core issues?
> srcN brings two things to the table, compared to srcset:
> 1. It handles viewport-switching better (easier to author, avoids repetition of image urls, allows bandwidth-driven decisions).
> 2. It handles art direction.
> Does everyone agree that these are useful and long-overdue problems to solve, and that the high-level approach of srcN (with <viewport-urls> syntax to handle viewport switching, and a layer of media queries above that) is the best (only) known solution to these?

Accepting the premises of these use cases, I'm not sure the given proposals are the *only* solutions, although they may be steps in the right direction. 

(1) Regarding viewport-urls syntax: it has too many numbers in it with no direct indication of what the numbers are. I've tried to learn it, but when I look at an example like this:

  <img src-1="100%; pic1.png 160, pic2.png 320, pic3.png 640, pic4.png 1280, pic5.png 2560">

Or like this:

  <img src-1="100% (640px) 50% (960px) 33%; 160.jpg 160, 320.jpg 320, 480.jpg 480, 640.jpg 640, 960.jpg 960, 1280.jpg 1280, 1920.jpg 1920">

I have to go back to the spec to figure out what each of the numbers means.

More information about the webkit-dev mailing list