<div dir="ltr">I think this discussion might be more fruitful at a vendor neutral forum, so I've started a thread out on the WHATWG: <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-November/041369.html">http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-November/041369.html</a></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 8, 2013 at 6:06 PM, John Mellor <span dir="ltr"><<a href="mailto:johnme@chromium.org" target="_blank">johnme@chromium.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>Most discussion so far seems to be bikeshedding the syntax. To make this more productive, can we focus on the core issues?<br></div><div><br></div><div>srcN brings two things to the table, compared to srcset:</div>
<div>1. It handles viewport-switching better (easier to author, avoids repetition of image urls, allows bandwidth-driven decisions).</div><div>2. It handles art direction.</div><div><br></div><div>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?</div>
</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 8, 2013 at 3:24 PM, Dean Jackson <span dir="ltr"><<a href="mailto:dino@apple.com" target="_blank">dino@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[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. ]<br>
<div><br>
On 7 Nov 2013, at 17:43, "Tab Atkins Jr." <<a href="mailto:jackalmage@gmail.com" target="_blank">jackalmage@gmail.com</a>> wrote:<br>
<br>
>> A proposal for a new paradigm of using multiple attributes deserves some resistance, careful consideration and exploration of alternatives. I feel my factual example of <path d> was flippantly tossed aside. So I responded in jest.<br>
><br>
> Apologies if you believed my response was flippant; it was short, but<br>
> serious and to the point. I explained why the <path d> example wasn't<br>
> very good - it's a single (albeit way overcomplicated) list of<br>
> commands. The src-N attributes already contain lists, so they're<br>
> comparable. I'm objecting to combining the src-N attributes into a<br>
> single attribute because that produces a *list of lists*, which is a<br>
> significant step further in mental complexity.<br>
<br>
</div>one of the things I liked about srcset is that in the most urgent case it is simply one extra attribute with one higher resolution image.<br>
<br>
once we get into structure and ordering and multiple options and art direction any of these attribute solutions looks horrible. I don't care whether it is one attribute or 99, it's a pain to understand. if you want structure, use markup. I'm tempted to think the <picture> element is a better solution for these advanced cases.<br>
<br>
fwiw path d is an attribute because we expected thousands of values in that and structure would have been too unwieldy.<br>
<span><font color="#888888"><br>
dean<br>
</font></span><div><div>_______________________________________________<br>
webkit-dev mailing list<br>
<a href="mailto:webkit-dev@lists.webkit.org" target="_blank">webkit-dev@lists.webkit.org</a><br>
<a href="https://lists.webkit.org/mailman/listinfo/webkit-dev" target="_blank">https://lists.webkit.org/mailman/listinfo/webkit-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
webkit-dev mailing list<br>
<a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
<a href="https://lists.webkit.org/mailman/listinfo/webkit-dev" target="_blank">https://lists.webkit.org/mailman/listinfo/webkit-dev</a><br>
<br></blockquote></div><br></div>