If both srcset and srcN were available for use today, as a developer I
would prefer srcN due to its syntax being easier to read, write and
maintain. However, what other alternatives could we use in place of the
number suffix? Is it at all possible to look into Cory's idea about having
multiple srcN attributes, along with a .srcList array?
<img srcN="(max-width: 400px) pic-small.jpg"
srcN="(max-width: 1000px) pic-medium.jpg"
src="pic-large.jpg">
On Fri, Sep 27, 2013 at 8:37 AM, Yoav Weiss <yoav@yoav.ws> wrote:
> The main question was "What is the use-case?", to which we failed to come
> up with an answer.
>
> Do you have a particular use for knowing which source was picked by the
> browser, other than testing?
>
>
> On Fri, Sep 27, 2013 at 3:34 PM, Cory Brown <oh.wise.man@gmail.com> wrote:
>
>> currentSrc is used on <video> and <audio> where multiple possible sources
>> exist. Why is this any different? Did Hixie explain his reasoning?
>>
>>
>> On Fri, Sep 27, 2013 at 9:15 AM, Marcos Caceres <w3c@marcosc.com> wrote:
>>
>>>
>>>
>>>
>>> On Friday, September 27, 2013 at 1:25 PM, Cory Brown wrote:
>>>
>>> > I believe src can treated as an attribute where as currentSrc can be
>>> treated as a property, meaning it reflects actual state.
>>>
>>>
>>> FWIW, I wasn't able to convince Hixie that currentSrc was a good idea
>>> for srcset. Collectively as a CG, we were unable to come up with a use case
>>> for it.
>>>
>>> The counter argument goes that you should really use developer tools for
>>> finding out what the current source of an attribute is (instead of script).
>>>
>>> --
>>> Marcos Caceres
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Cory Brown
>>
>
>
Received on Friday, 27 September 2013 14:02:02 UTC