Re: [selectors] Finding a way to run "complete" profile selectors in CSS

On Fri, Jul 12, 2013 at 11:18 AM, Timmy <timmywillisn@gmail.com> wrote:
> On Jul 12, 2013, at 2:03 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>> Then random selectors across your stylesheet would run slowly, and it
>> would be difficult to tell what was happening unless you were very
>> familiar with what things are in what profile.
>
> This is true, but it is a trade-off. There is also confusion if selectors are ever moved from the complete profile to the fast profile

Not really.  All selectors work in the deferred block; things moving
to the fast profile just means that in newer browsers you can use
those particular selectors everywhere else, too.

>  or if there's any ambiguity about which selectors should be deferred.

That's a spec bug if it occurs.

> Is it a syntax error to put selectors in the fast profile in the @defer at-rule? What happens when they get switched? Do fast selectors get deferred in the @defer rule even though they don't need to be? These are questions that don't matter if the selectors that need to be deferred get deferred automatically and the user has opted into that behavior.

It's not a syntax error.  Yes, they get deferred.  Don't put your
entire stylesheet into a deferred block to avoid having to think about
these things unless you're willing to accept extra-slow selector
matching.

~TJ

Received on Friday, 12 July 2013 18:22:58 UTC