Re: What do we do with picture?

For what it's worth. I agree with Anselm. From a developers perspective, I
find <picture> to be far more maintainable and readable. srcN may be easier
to implement on the browser, but picture is easier to read and write, it is
a different element by design (It really serves a different purpose than
<img> which represents a single instance of a specific image where
<picture> represents a single instance of any number of possible images.) I
understand browser vendor's concerns, and they have to look out for their
interests, but on the dev side, <picture> seems like the way forward to me.

Cory


On Thu, Oct 17, 2013 at 10:45 AM, Marcos Caceres <w3c@marcosc.com> wrote:

>
>
> On Thursday, October 17, 2013 at 3:40 PM, Yoav Weiss wrote:
>
> > I agree with publishing as a note, for all the reasons you mentioned.
> >
> > Are there similar pressures to move the use-cases document forward? Or
> is this just for specs?
> >
>
> Same with use cases. We can publish as a Note and we can continue to
> update it if we feel like it. The use cases document has been very useful
> and I can imagine it will continue to be so in the future. However, it's
> not a "spec".
>
>
>
>


-- 
Cory Brown