[webkit-dev] The SrcN responsive images proposal

[Elliott Sprehn]

On Mon, Nov 4, 2013 at 4:55 PM, Ryosuke Niwa <rniwa at webkit.org> wrote:

> On Mon, Nov 4, 2013 at 3:12 PM, Elliott Sprehn <esprehn at chromium.org>wrote:
>
>> On Mon, Nov 4, 2013 at 2:19 PM, Ryosuke Niwa <rniwa at 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 should use exactly one attribute for this
>>> feature.
>>>
>>
>> Can you explain what this optimization is? It's difficult to figure out
>> how to address your issues without knowing what optimization it prevents.
>>
>
> I'm not sure if I wasn't clear here but I'm saying that having an upper
> bound of 9 or 99 would address the concern of not being able to implement
> the particular optimization we're considering.
>

Yeah; what optimization do you plan to implement though?


>
> Completely separate from that concern, I don't want us to add more than
> one content attribute to address the use cases src-N proposal addresses for
> the API's sake although I wouldn't firmly object to it if there is a broad
> consensus that this is a feature we want in WebKit.
>
> However, I don't think that there is such a consensus amongst the WebKit
> community yet as far as I've been following this thread. As such, I DO NOT
> support implementing this feature in WebKit.
>
> - R. Niwa
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20131104/63923e0e/attachment.html>