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

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

From: Anselm Hannemann <info@anselm-hannemann.com>
Date: Tue, 12 Nov 2013 09:15:34 +0100
Message-Id: <B7B61F96-DE01-467F-823A-A7BEB708A059@anselm-hannemann.com>
To: Adam Barth <w3c@adambarth.com>
Cc: "Jukka K. Korpela" <jkorpela@cs.tut.fi>, whatwg <whatwg@lists.whatwg.org>
On 12.11.2013, at 09:11, 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?
> 
> Adam


Dear Adam,

no, a preload scanner will never (okay, never say never) interpret CSS.
This is against the rule of it to improve performance before interpreting layout.
This also has been answered more in detail several times now so if you need
more evidence, please look up in the archives. Thanks :)

-Anselm
Received on Tuesday, 12 November 2013 08:15:58 UTC

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