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

Re: What do we do with picture?

From: Aaron Grogg <aarontgrogg@gmail.com>
Date: Fri, 18 Oct 2013 06:38:06 +0200
Message-ID: <CAMZSREBFysw7ZcR92VH+Zax7DQiH4JCANGhJ7_VR-+1ZX5ZAbg@mail.gmail.com>
To: Marcos Caceres <w3c@marcosc.com>
Cc: (wrong string) „ski <kornel@geekhood.net>, Anselm Hannemann <info@anselm-hannemann.com>, public-respimg@w3.org
>From a purest-view, I really prefer <picture>.  I think the code is more
readable, more memorable, and also like how the <picture> syntax mirrors
<video>.  It almost (gasp!) feels like consistency...

>From a pragmatist-view, I really want something yesterday, and if either
srcset or srcN is going to get us to a responsive image solution faster,
then "ok, whatever".  I know, however, that I am *always* going to have to
look up syntaxes for both of these solutions, but then I don't build
websites for me, I build them for users.

So, I guess, whatever gets us to a solution faster, I'm good with.


*Aaron T. Grogg
*website: http://aarontgrogg.com/*
*email: aarontgrogg@gmail.com
*twitter: @aarontgrogg
*skype: aarontgrogg*

On Fri, Oct 18, 2013 at 1:30 AM, Marcos Caceres <w3c@marcosc.com> wrote:

> On Thursday, October 17, 2013 at 11:32 PM, Simon Pieters wrote:
> > Similarly for crossorigin, usemap, ismap, width, height, .naturalWidth,
> > .naturalHeight, .complete, painting on a canvas, interaction with CSS
> > stuff like object-fit, UI features like the context menu, and so on.
> This can't be understated. There are all massive free wins that we had
> completely left out of picture due to complexity.
> --
> Marcos Caceres
Received on Friday, 18 October 2013 09:51:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:06:10 UTC