W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2012

Re: [whatwg] Features for responsive Web design

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Fri, 18 May 2012 14:07:18 +1000
Message-ID: <CAHp8n2nj5NBVZpTagiR_YVUGUfVChW_fP7KpE+CPObqO+Q_FCA@mail.gmail.com>
To: Maciej Stachowiak <mjs@apple.com>
Cc: whatwg <whatwg@lists.whatwg.org>, Henri Sivonen <hsivonen@iki.fi>, Matthew Wilcox <mail@matthewwilcox.com>, PJ McCormick <pj@mynameispj.com>
On Thu, May 17, 2012 at 3:26 PM, Maciej Stachowiak <mjs@apple.com> wrote:
>
> On May 16, 2012, at 9:39 PM, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote:
>
>> On Wed, May 16, 2012 at 10:55 PM, Matthew Wilcox <mail@matthewwilcox.com> wrote:
>>> Chalk me up as another making that mistake. Properties on elements
>>> usually describe a property of the element. Not a property of
>>> something else (like the viewport).
>>
>> If it does indeed rely on a rendering issue (like the size of the
>> viewport), wouldn't it make more sense to make it a CSS feature? I
>> think that would be less confusing and follow better the established
>> separation of layout in html, styling(/rendering) in CSS.
>
> CSS can handle this fine for presentational images (such as CSS background images). But it's not obvious that it's the best way to influence selection of content images references from <img>. Content images are meaningful, not just stylistic, so their variants are meaningful too (even if the choice of variant is influenced by presentational issues).

Hmm... I'm not actually talking about having the images specified in CSS.
I don't actually have a suggestion for how that would look - it seems
the list of resources needs to be given in HTML, but the selection
between them should be done in CSS.

Not sure this helps ... but since we're brainstorming...

Silvia.
Received on Friday, 18 May 2012 04:08:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:08 GMT