W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2013

Re: [whatwg] <imgset> responsive imgs proposition (Re: The src-N proposal)

From: Ryosuke Niwa <rniwa@apple.com>
Date: Tue, 12 Nov 2013 21:33:07 +0800
Message-id: <2AA6D223-3F3D-4D0F-A642-59AC92FCA598@apple.com>
To: Adam Barth <w3c@adambarth.com>
Cc: "Jukka K. Korpela" <jkorpela@cs.tut.fi>, whatwg <whatwg@lists.whatwg.org>
On Nov 12, 2013, at 4:11 PM, Adam Barth <w3c@adambarth.com> wrote:
> On Tue, Nov 12, 2013 at 12:08 AM, Jukka K. Korpela <jkorpela@cs.tut.fi> wrote:
>> 2013-11-12 9:58, Adam Barth wrote:
>>> Unfortunately, we can't add new tags to head.  If the parser sees a
>>> tag it doesn't recognize in the head, it creates a fake body tag and
>>> pushes the tag down into the body.
>> But you could use <style type=text/foobar>...</style>, with a suitable value
>> for foobar, like x-imgset. This could even be handled with a polyfill in old
>> browsers (JavaScript code that reads such elements and interprets their
>> content).
> Maybe there's a CSS solution to this problem?  Do we just need to make
> the preload scanner smarter about interpreting CSS?

In fact, Id argue that CSS will be a better fit to address art direction use case since its purely presentational.

We could define some ways to list set of images that could be replaced for a given img element in HTML and then let CSS pick which one to use for example.

- R. Niwa
Received on Tuesday, 12 November 2013 13:33:38 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:14 UTC