Re: [webkit-dev] The SrcN responsive images proposal

On Nov 8, 2013, at 9:06 AM, John Mellor 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

Re: [webkit-dev] The SrcN responsive images proposal

On Fri, Nov 8, 2013 at 8:44 PM, Maciej Stachowiak wrote: > > On Nov 7, 2013, at 2:38 PM, Tab Atkins Jr. wrote: > > > On Thu, Nov 7, 2013 at 9:24 AM, Timothy Hatcher > wrote: > >> As I replied before, there should only be one attribute — srcset. > > > > I have a serious suggestion - could we ren

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 7, 2013, at 2:38 PM, Tab Atkins Jr. wrote: > On Thu, Nov 7, 2013 at 9:24 AM, Timothy Hatcher wrote: >> As I replied before, there should only be one attribute — srcset. > > I have a serious suggestion - could we rename srcset to src-n > (literally, "src-n"), and then just ship it? This

Re: [webkit-dev] The SrcN responsive images proposal

I think this discussion might be more fruitful at a vendor neutral forum, so I've started a thread out on the WHATWG: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-November/041369.html On Fri, Nov 8, 2013 at 6:06 PM, John Mellor wrote: > Most discussion so far seems to be bikesheddin

Re: [webkit-dev] The SrcN responsive images proposal

On Friday, November 8, 2013, Dean Jackson wrote: > [And the holy book sayeth cursed is she who participates in standards > email, doomed forever to receive email in CC and being unable to sleep at > night. ] > > On 7 Nov 2013, at 17:43, "Tab Atkins Jr." > > wrote: > > >> A proposal for a new parad

Re: [webkit-dev] The SrcN responsive images proposal

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 de

Re: [webkit-dev] The SrcN responsive images proposal

[And the holy book sayeth cursed is she who participates in standards email, doomed forever to receive email in CC and being unable to sleep at night. ] On 7 Nov 2013, at 17:43, "Tab Atkins Jr." wrote: >> A proposal for a new paradigm of using multiple attributes deserves some >> resistance, c

Re: [webkit-dev] The SrcN responsive images proposal

On Fri, Nov 8, 2013 at 12:50 AM, Timothy Hatcher wrote: > On Nov 7, 2013, at 2:43 PM, Tab Atkins Jr. wrote: > > I'm pretty sure the argument is almost entirely around hand-authoring, > where experience with style='' shows that lists-of-lists are bad. > > > Until you are dealing with dozens of im

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 7, 2013, at 6:36 PM, Timothy Hatcher wrote: > On Nov 7, 2013, at 5:43 PM, Tab Atkins Jr. wrote: > >> I'm objecting to combining the src-N attributes into a >> single attribute because that produces a *list of lists*, which is a >> significant step further in mental complexity. > > We c

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 7, 2013, at 5:43 PM, Tab Atkins Jr. wrote: > I'm objecting to combining the src-N attributes into a > single attribute because that produces a *list of lists*, which is a > significant step further in mental complexity. We can agree to disagree then. I do not support the use of multiple a

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Nov 7, 2013 at 5:03 PM, Maciej Stachowiak wrote: > Do you claim that using multiple numbered possibly out-of-order attributes as > one level of list hierarchy is a smaller mental tax than an extra delimiter? > Seems clearly the opposite to me. Of course it does when you phrase one with

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Nov 7, 2013 at 4:50 PM, Timothy Hatcher wrote: > On Nov 7, 2013, at 4:28 PM, Tab Atkins Jr. wrote: > >> On Thu, Nov 7, 2013 at 3:43 PM, Timothy Hatcher wrote: >>> On Nov 7, 2013, at 2:38 PM, Tab Atkins Jr. wrote: I have a serious suggestion - could we rename srcset to src-n (l

Re: [webkit-dev] The SrcN responsive images proposal

> On Nov 7, 2013, at 4:27 PM, "Tab Atkins Jr." wrote: > >> On Thu, Nov 7, 2013 at 3:39 PM, Timothy Hatcher wrote: >>> On Nov 7, 2013, at 2:22 PM, Tab Atkins Jr. wrote: >>> srcset's parsing algorithm *cannot* be extended in the future. I gave >>> an example of how it would fail over on blink-d

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 7, 2013, at 4:28 PM, Tab Atkins Jr. wrote: > On Thu, Nov 7, 2013 at 3:43 PM, Timothy Hatcher wrote: >> On Nov 7, 2013, at 2:38 PM, Tab Atkins Jr. wrote: >>> I have a serious suggestion - could we rename srcset to src-n >>> (literally, "src-n"), and then just ship it? This puns in three

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 7, 2013, at 4:27 PM, Tab Atkins Jr. wrote: > On Thu, Nov 7, 2013 at 3:39 PM, Timothy Hatcher wrote: >> On Nov 7, 2013, at 2:22 PM, Tab Atkins Jr. wrote: >>> srcset's parsing algorithm *cannot* be extended in the future. I gave >>> an example of how it would fail over on blink-dev; I can

Re: [webkit-dev] The SrcN responsive images proposal

On 11/7/13, 4:27 PM, Tab Atkins Jr. wrote: On Thu, Nov 7, 2013 at 3:39 PM, Timothy Hatcher wrote: On Nov 7, 2013, at 2:22 PM, Tab Atkins Jr. wrote: srcset's parsing algorithm *cannot* be extended in the future. I gave an example of how it would fail over on blink-dev; I can reproduce it here

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Nov 7, 2013 at 3:43 PM, Timothy Hatcher wrote: > On Nov 7, 2013, at 2:38 PM, Tab Atkins Jr. wrote: >> I have a serious suggestion - could we rename srcset to src-n >> (literally, "src-n"), and then just ship it? This puns in three >> interesting ways: [...] >> This'll let us ship now, an

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Nov 7, 2013 at 3:39 PM, Timothy Hatcher wrote: > On Nov 7, 2013, at 2:22 PM, Tab Atkins Jr. wrote: >> srcset's parsing algorithm *cannot* be extended in the future. I gave >> an example of how it would fail over on blink-dev; I can reproduce it >> here if necessary. > > I don't subscribe

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 7, 2013, at 3:49 PM, Elliott Sprehn wrote: > It is shipping in Safari 6.1, 7 and iOS 7. That ship has sailed. > > Can you please clarify this, I just tested in Safari 6.1 and 7 and I don't > see srcset on HTMLImageElement. What do you mean it's shipped? > > document.createElement('img')

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Nov 7, 2013 at 3:39 PM, Timothy Hatcher wrote: > On Nov 7, 2013, at 2:22 PM, Tab Atkins Jr. wrote: > > > On Thu, Nov 7, 2013 at 9:24 AM, Timothy Hatcher > wrote: > >> On Nov 6, 2013, at 4:26 PM, John Mellor wrote: > >>> I've suggested before that the attributes could be combined if tha

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 7, 2013, at 2:43 PM, Tab Atkins Jr. wrote: > I'm pretty sure the argument is almost entirely around hand-authoring, > where experience with style='' shows that lists-of-lists are bad. Until you are dealing with dozens of images per tag. That is untenable one image heavy sites and tools

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 7, 2013, at 2:38 PM, Tab Atkins Jr. wrote: > On Thu, Nov 7, 2013 at 9:24 AM, Timothy Hatcher wrote: > >> As I replied before, there should only be one attribute — srcset. > > I have a serious suggestion - could we rename srcset to src-n > (literally, "src-n"), and then just ship it? Th

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 7, 2013, at 2:22 PM, Tab Atkins Jr. wrote: > On Thu, Nov 7, 2013 at 9:24 AM, Timothy Hatcher wrote: >> On Nov 6, 2013, at 4:26 PM, John Mellor wrote: >>> I've suggested before that the attributes could be combined if that's >>> considered simpler. My only concern is that most developers

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Nov 7, 2013 at 2:31 PM, Noam Rosenthal wrote: >> > Designing this proposal around code formatting is a non-issue in my >> > opinion >> > and it surely didn't stop SVG from providing just one "d" attribute for >> > . Following the your logic, it should be d-N. Sure, >> > is >> > primarily

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Nov 7, 2013 at 9:24 AM, Timothy Hatcher wrote: > As I replied before, there should only be one attribute — srcset. I have a serious suggestion - could we rename srcset to src-n (literally, "src-n"), and then just ship it? This puns in three interesting ways: 1. If src-N is never accepte

Re: [webkit-dev] The SrcN responsive images proposal

> > Designing this proposal around code formatting is a non-issue in my > opinion > > and it surely didn't stop SVG from providing just one "d" attribute for > > . Following the your logic, it should be d-N. Sure, is > > primarily meant to be written by software. > > Please don't try to use reduct

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Nov 7, 2013 at 9:24 AM, Timothy Hatcher wrote: > On Nov 6, 2013, at 4:26 PM, John Mellor wrote: >> I've suggested before that the attributes could be combined if that's >> considered simpler. My only concern is that most developers aren't used to >> putting line breaks in html attributes,

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 6, 2013, at 4:26 PM, John Mellor wrote: > I've suggested before that the attributes could be combined if that's > considered simpler. My only concern is that most developers aren't used to > putting line breaks in html attributes, so might feel obliged to put all the > alternatives on o

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Nov 7, 2013 at 3:32 AM, Benjamin Poulain wrote: > On 11/6/13, 3:24 PM, Yoav Weiss wrote: > >> >> On Wed, Nov 6, 2013 at 11:33 PM, Benjamin Poulain > > wrote: >> >> On 11/6/13, 10:53 AM, John Mellor wrote: >> >> On Sun, Oct 20, 2013 at 2:00 AM, Maciej

Re: [webkit-dev] The SrcN responsive images proposal

On 11/6/13, 3:24 PM, Yoav Weiss wrote: On Wed, Nov 6, 2013 at 11:33 PM, Benjamin Poulain mailto:benja...@webkit.org>> wrote: On 11/6/13, 10:53 AM, John Mellor wrote: On Sun, Oct 20, 2013 at 2:00 AM, Maciej Stachowiak mailto:m...@apple.com>

Re: [webkit-dev] The SrcN responsive images proposal

On Wed, Nov 6, 2013 at 8:00 PM, Maciej Stachowiak wrote: > (...) > > I know there are explanations for how src-N got to be as complex as it is. > However, the following counterpoints come to mind: > > (a) The complexity is not well-contained; some of it leaks out even if you > want to do somethin

Re: [webkit-dev] The SrcN responsive images proposal

On Wed, Nov 6, 2013 at 11:33 PM, Benjamin Poulain wrote: > On 11/6/13, 10:53 AM, John Mellor wrote: > >> On Sun, Oct 20, 2013 at 2:00 AM, Maciej Stachowiak > > wrote: >> > >> > My initial impression is that it seems a bit overengineered. >> >> I sympathize. The issue of sr

Re: [webkit-dev] The SrcN responsive images proposal

On Wed, Nov 6, 2013 at 9:00 PM, Maciej Stachowiak wrote: > > > (b) I am dubious of some of the use cases proposed as essential for src-N > that ratchet up the complexity. For example, your case #2 of > viewport-switching > Viewport switching is very common in almost any responsive design. > ,

Re: [webkit-dev] The SrcN responsive images proposal

On 11/6/13, 10:53 AM, John Mellor wrote: On Sun, Oct 20, 2013 at 2:00 AM, Maciej Stachowiak mailto:m...@apple.com>> wrote: > > My initial impression is that it seems a bit overengineered. I sympathize. The issue of srcN appearing to be a complex solution to a seemingly simple problem came up a

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 6, 2013, at 10:53 AM, John Mellor wrote: > On Sun, Oct 20, 2013 at 2:00 AM, Maciej Stachowiak wrote: > > > > My initial impression is that it seems a bit overengineered. > > I sympathize. The issue of srcN appearing to be a complex solution to a > seemingly simple problem came up again

Re: [webkit-dev] The SrcN responsive images proposal

On Sun, Oct 20, 2013 at 2:00 AM, Maciej Stachowiak wrote: > > My initial impression is that it seems a bit overengineered. I sympathize. The issue of srcN appearing to be a complex solution to a seemingly simple problem came up again on IRC chatting to rniwa, so I thought I'd try to explain this

Re: [webkit-dev] The SrcN responsive images proposal

On 5 Nov 2013, at 9:55 am, Timothy Hatcher wrote: > On Nov 5, 2013, at 2:18 AM, John Mellor wrote: > >> > > I prefer this over multiple attributes. It is a syntax that needs little > explanation before you can read it and use it. It also expands the existing > srcset instead of confusing t

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 5, 2013, at 2:18 AM, John Mellor wrote: > I prefer this over multiple attributes. It is a syntax that needs little explanation before you can read it and use it. It also expands the existing srcset instead of confusing things with other attributes. srcN is also too fiddly. If you want

Re: [webkit-dev] The SrcN responsive images proposal

On Nov 5, 2013, at 11:18 AM, John Mellor mailto:joh...@chromium.org>> wrote: On Mon, Nov 4, 2013 at 10:19 PM, Ryosuke Niwa mailto:rn...@webkit.org>> wrote: 99 is a very high upper bound while it would still allow us to implement the optimization we're thinking of. I'm of the opinion that we s

Re: [webkit-dev] The SrcN responsive images proposal

On Mon, Nov 4, 2013 at 10:19 PM, Ryosuke Niwa wrote: > 99 is a very high upper bound while it would still allow us to implement > the optimization we're thinking of. > > I'm of the opinion that we should use exactly one attribute for this > feature. > The thing is, srcN isn't a list, it's a list

Re: [webkit-dev] The SrcN responsive images proposal

On Mon, Nov 4, 2013 at 5:07 PM, Elliott Sprehn wrote: > On Mon, Nov 4, 2013 at 4:55 PM, Ryosuke Niwa wrote: > >> On Mon, Nov 4, 2013 at 3:12 PM, Elliott Sprehn wrote: >> >>> On Mon, Nov 4, 2013 at 2:19 PM, Ryosuke Niwa wrote: >>> 99 is a very high upper bound while it would still allow us

Re: [webkit-dev] The SrcN responsive images proposal

On Mon, Nov 4, 2013 at 4:55 PM, Ryosuke Niwa wrote: > On Mon, Nov 4, 2013 at 3:12 PM, Elliott Sprehn wrote: > >> On Mon, Nov 4, 2013 at 2:19 PM, Ryosuke Niwa wrote: >> >>> 99 is a very high upper bound while it would still allow us to implement >>> the optimization we're thinking of. >>> >>> I'm

Re: [webkit-dev] The SrcN responsive images proposal

On Mon, Nov 4, 2013 at 3:12 PM, Elliott Sprehn wrote: > On Mon, Nov 4, 2013 at 2:19 PM, Ryosuke Niwa wrote: > >> 99 is a very high upper bound while it would still allow us to implement >> the optimization we're thinking of. >> >> I'm of the opinion that we should use exactly one attribute for t

Re: [webkit-dev] The SrcN responsive images proposal

On Mon, Nov 4, 2013 at 2:19 PM, Ryosuke Niwa wrote: > 99 is a very high upper bound while it would still allow us to implement > the optimization we're thinking of. > > I'm of the opinion that we should use exactly one attribute for this > feature. > > > Can you explain what this optimization is?

Re: [webkit-dev] The SrcN responsive images proposal

99 is a very high upper bound while it would still allow us to implement the optimization we're thinking of. I'm of the opinion that we should use exactly one attribute for this feature. - R. Niwa On Mon, Nov 4, 2013 at 2:04 PM, Yoav Weiss wrote: > > > > On Thu, Oct 24, 2013 at 9:33 AM, Ryosuk

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Oct 24, 2013 at 9:33 AM, Ryosuke Niwa wrote: > On Wed, Oct 23, 2013 at 11:24 PM, Yoav Weiss wrote: > >> On Wed, Oct 23, 2013 at 10:22 PM, Ryosuke Niwa wrote: >> >>> On Tue, Oct 22, 2013 at 1:50 PM, Tab Atkins Jr. wrote: >>> On Sun, Oct 20, 2013 at 10:07 AM, Antti Koivisto wro

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Oct 24, 2013 at 7:06 PM, Maciej Stachowiak wrote: > > On Oct 23, 2013, at 11:24 PM, Yoav Weiss wrote: > > > On Wed, Oct 23, 2013 at 10:22 PM, Ryosuke Niwa wrote: > >> On Tue, Oct 22, 2013 at 1:50 PM, Tab Atkins Jr. wrote: >> >>> On Sun, Oct 20, 2013 at 10:07 AM, Antti Koivisto >>> wrot

Re: [webkit-dev] The SrcN responsive images proposal

On Oct 24, 2013, at 1:35 AM, Michael[tm] Smith wrote: > Ryosuke Niwa , 2013-10-23 13:22 -0700: > >> On Tue, Oct 22, 2013 at 1:50 PM, Tab Atkins Jr. wrote: >>> On Sun, Oct 20, 2013 at 10:07 AM, Antti Koivisto wrote: Ignoring other aspects of this, the idea of making attribute name an

Re: [webkit-dev] The SrcN responsive images proposal

On Oct 23, 2013, at 11:24 PM, Yoav Weiss wrote: > > On Wed, Oct 23, 2013 at 10:22 PM, Ryosuke Niwa wrote: > On Tue, Oct 22, 2013 at 1:50 PM, Tab Atkins Jr. wrote: > On Sun, Oct 20, 2013 at 10:07 AM, Antti Koivisto wrote: > > Ignoring other aspects of this, the idea of making attribute name a

Re: [webkit-dev] The SrcN responsive images proposal

Ryosuke Niwa , 2013-10-23 13:22 -0700: > On Tue, Oct 22, 2013 at 1:50 PM, Tab Atkins Jr. wrote: > > On Sun, Oct 20, 2013 at 10:07 AM, Antti Koivisto wrote: > > > Ignoring other aspects of this, the idea of making attribute name an > > > enumeration is somewhat distasteful. It will require ugly sp

Re: [webkit-dev] The SrcN responsive images proposal

On Wed, Oct 23, 2013 at 11:24 PM, Yoav Weiss wrote: > On Wed, Oct 23, 2013 at 10:22 PM, Ryosuke Niwa wrote: > >> On Tue, Oct 22, 2013 at 1:50 PM, Tab Atkins Jr. wrote: >> >>> On Sun, Oct 20, 2013 at 10:07 AM, Antti Koivisto >>> wrote: >>> > Ignoring other aspects of this, the idea of making att

Re: [webkit-dev] The SrcN responsive images proposal

On Wed, Oct 23, 2013 at 10:22 PM, Ryosuke Niwa wrote: > On Tue, Oct 22, 2013 at 1:50 PM, Tab Atkins Jr. wrote: > >> On Sun, Oct 20, 2013 at 10:07 AM, Antti Koivisto wrote: >> > Ignoring other aspects of this, the idea of making attribute name an >> > enumeration is somewhat distasteful. It will

Re: [webkit-dev] The SrcN responsive images proposal

On Tue, Oct 22, 2013 at 1:50 PM, Tab Atkins Jr. wrote: > On Sun, Oct 20, 2013 at 10:07 AM, Antti Koivisto wrote: > > Ignoring other aspects of this, the idea of making attribute name an > > enumeration is somewhat distasteful. It will require ugly special > parsing. > > The platform has plenty of

Re: [webkit-dev] The SrcN responsive images proposal

On Tue, Oct 22, 2013 at 11:50 PM, Tab Atkins Jr. wrote: > The parsing aspect isn't particularly new - parsing data-* attributes > presents the same problem. You just need to filter the list of > data-* attributes are not parsed. > attributes on the element to look for things with a src- prefix

Re: [webkit-dev] The SrcN responsive images proposal

"Tab Atkins Jr." , 2013-10-22 14:50 -0600: > As I've argued before, I think "making validators easy to write" > is a concern that's very, very low on the priority of constituencies. So don't keep framing it that way, then. It's misleading. I'm not arguing for making validators easier to write a

Re: [webkit-dev] The SrcN responsive images proposal

On Oct 22, 2013, at 1:50 PM, Tab Atkins Jr. wrote: > On Sat, Oct 19, 2013 at 7:00 PM, Maciej Stachowiak wrote: >> My initial impression is that it seems a bit overengineered. > > Can you elaborate on these concerns? - The syntax is effectively a list of lists, the outer level being implicit i

Re: [webkit-dev] The SrcN responsive images proposal

On Sat, Oct 19, 2013 at 7:00 PM, Maciej Stachowiak wrote: > My initial impression is that it seems a bit overengineered. Can you elaborate on these concerns? I tried to find the simplest set of features that solves the use-cases I was presented with in a good way: * lists of urls and resolution

Re: [webkit-dev] The SrcN responsive images proposal

Benjamin Poulain , 2013-10-20 13:08 -0700: > On 10/20/13, 9:07 AM, Antti Koivisto wrote: > > Ignoring other aspects of this, the idea of making attribute name an > > enumeration is somewhat distasteful. It will require ugly special > > parsing. The platform has plenty of attribute values that are

Re: [webkit-dev] The SrcN responsive images proposal

On Sun, Oct 20, 2013 at 11:08 PM, Benjamin Poulain wrote: > On 10/20/13, 9:07 AM, Antti Koivisto wrote: > > Ignoring other aspects of this, the idea of making attribute name an > > enumeration is somewhat distasteful. It will require ugly special > > parsing. The platform has plenty of attribute v

Re: [webkit-dev] The SrcN responsive images proposal

On 10/20/13, 9:07 AM, Antti Koivisto wrote: > Ignoring other aspects of this, the idea of making attribute name an > enumeration is somewhat distasteful. It will require ugly special > parsing. The platform has plenty of attribute values that are lists already. I was thinking the same thing last n

Re: [webkit-dev] The SrcN responsive images proposal

Ignoring other aspects of this, the idea of making attribute name an enumeration is somewhat distasteful. It will require ugly special parsing. The platform has plenty of attribute values that are lists already. antti On Sun, Oct 20, 2013 at 4:00 AM, Maciej Stachowiak wrote: > My initial im

Re: [webkit-dev] The SrcN responsive images proposal

Le 20 oct. 2013 à 14:39, Yoav Weiss a écrit : > On Oct 20, 2013 11:31 AM, "PERIER Romain" wrote: > > > > Hi all, > > srcset is not complicated enough for a web developer? why do you want to > > add complexity for the developer ? The srcset specification already convers > > DRP switching and

Re: [webkit-dev] The SrcN responsive images proposal

On Oct 20, 2013 11:31 AM, "PERIER Romain" wrote: > > Hi all, > srcset is not complicated enough for a web developer? why do you want to add complexity for the developer ? The srcset specification already convers DRP switching and viewport The reasoning behind the new proposal was detailed by Joh

Re: [webkit-dev] The SrcN responsive images proposal

Hi all, srcset is not complicated enough for a web developer? why do you want to add complexity for the developer ? The srcset specification already convers DRP switching and viewport (not implemented yet, but it is planned, it is in my todo list) why don't you propose improvements to the origina

Re: [webkit-dev] The SrcN responsive images proposal

My initial impression is that it seems a bit overengineered. - Maciej > On Oct 19, 2013, at 4:39 PM, Yoav Weiss wrote: > > Hello WebKiteers, > > I'd like to get the project's opinion on a recent responsive image proposal > by Tab Atkins dubbed srcN: > http://tabatkins.github.io/specs/respim

[webkit-dev] The SrcN responsive images proposal

Hello WebKiteers, I'd like to get the project's opinion on a recent responsive image proposal by Tab Atkins dubbed srcN: http://tabatkins.github.io/specs/respimg/Overview.html This proposal covers all the major responsive images use-cases: DPR based resource selection, viewport dimensions based r