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

Re: [whatwg] An alternative to <picture> and srcset, is this realistic?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 14 May 2012 09:59:37 -0700
Message-ID: <CAAWBYDCjZqX1B6T6j-eh4=26D_wg1oO4tdBnY2Q3DT+iwZ--Tg@mail.gmail.com>
To: Matthew Wilcox <mail@matthewwilcox.com>
Cc: WHATWG List <whatwg@whatwg.org>
On Mon, May 14, 2012 at 9:31 AM, Matthew Wilcox <mail@matthewwilcox.com> wrote:
> All good points, thanks. Sorry I'd missed you saying <style> rather
> than <link/>, my bad!
>
> I had assumed that we would be able to take the logic for resolving
> media query applicability directly from that in CSS, which is why I
> have not given it any further thought. It seemed like a solved issue.

Heh, it *is* solved by CSS, it's just that the solution is "somewhere
between none and all of them apply", which works for CSS but not for
yours. ^_^

On Mon, May 14, 2012 at 9:46 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 5/14/12 11:55 AM, Tab Atkins Jr. wrote:
>>
>> That's why I mentioned an inline<style>  at the top of the<body>  -
>> I'm not sure if browsers skip past that when building the tree or not,
>
>
> They certainly skip past such things when prefetching.
>
> Putting information that needs to affect prefetching in elements where the
> HTML tokenizer can extract it is vastly better than putting it into elements
> where it can't (like <style>).

That's what I was afraid of.  All right, then, ignore that part of the
suggestion.  This should live in HTML if it lives anywhere.

~TJ
Received on Monday, 14 May 2012 17:00:34 GMT

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