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

Re: srcN - Alternative to picture and srcset

From: Cory Brown <oh.wise.man@gmail.com>
Date: Fri, 27 Sep 2013 09:34:52 -0400
Message-ID: <CAKxo9DprzXx1Pe+5s9_14GD-N3dFLqC57m-Wimwsnxw17tAC5g@mail.gmail.com>
To: Marcos Caceres <w3c@marcosc.com>
Cc: 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>
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:35:20 UTC

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