W3C home > Mailing lists > Public > www-style@w3.org > March 2013

Re: The :min-width/:max-width pseudo-classes

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 21 Mar 2013 12:24:24 -0700
Message-ID: <CAAWBYDBfMPJxBvYcKEQSW2MbGoW3uULYsNxfMTpQeEcC=uCsgQ@mail.gmail.com>
To: Elliott Sprehn <esprehn@gmail.com>
Cc: Fran├žois REMY <francois.remy.dev@outlook.com>, "www-style@w3.org" <www-style@w3.org>
On Thu, Mar 21, 2013 at 12:08 PM, Elliott Sprehn <esprehn@gmail.com> wrote:
> On Wed, Mar 20, 2013 at 5:41 PM, Fran├žois REMY
> <francois.remy.dev@outlook.com> wrote:
>> I'm thinking about adding this proposal in my Local Viewport proposal
>> draft in the near future, but I would love to get further feedback on the
>> feasibility and the timeframe in which we can hope to get the feature
>> implemented. I'm pretty sure that, depending on that, the importance of
>> optimizing the 'on layout updated' event loop will prove more or less
>> important.
> This doesn't seem very easy to implement because it breaks the sequential
> processing model:
> 1. resolve style on elements such that you have a flattened set of
> properties.
> 2. layout the elements if things are different then the last time we did
> step 1.
> The "viewport" is a magical thing outside the <html> element so when you
> resize it we can just execute step 1 to pick new selectors based on queries.
> Having pseudo classes that match conditionally based on the layout of some
> ancestor breaks this model since now you need to keep executing step 1 while
> doing step 2.
> This would be a big undertaking in Webkit so I don't think it falls anywhere
> in the near future.

The nice quality of it, though, is that by the very nature of the
"viewport element", you can defer the layout of the children until
you've gotten all the information necessary to evaluate those pseudos.
 I suspect this might map to something like preventing the children
from generating renderers until the parent is laid out, sorta like if
the children were all display:none and then switch to display:non-none
at the end of the first layout pass.

Yes, it's still interleaving, but it's not quite as bad as you may be thinking.

Received on Thursday, 21 March 2013 19:25:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:27 UTC