W3C home > Mailing lists > Public > public-respimg@w3.org > September 2013

Re: srcN - Alternative to picture and srcset

From: Yoav Weiss <yoav@yoav.ws>
Date: Fri, 27 Sep 2013 15:37:53 +0200
Message-ID: <CACj=BEjY=P-YfA+dpX1nfWN63GeoAtHGYAfUst3JYAO0zv6xVw@mail.gmail.com>
To: Cory Brown <oh.wise.man@gmail.com>
Cc: Marcos Caceres <w3c@marcosc.com>, Robin Berjon <robin@w3.org>, Attiks <attiks@gmail.com>, Shane Hudson <Shane@shanehudson.net>, Marcos Caceres <marcos@marcosc.com>, "public-respimg@w3.org" <public-respimg@w3.org>, "Tab Atkins Jr." <jackalmage@gmail.com>
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 13:38:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:12:40 UTC