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

On Fri, Jul 12, 2013 at 11:32 AM, Timmy <timmywillisn@gmail.com> wrote:
> On Jul 12, 2013, at 2:22 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
>> 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.
>
> Ok, except it would be really nice not to have to think about these things. The spec keeps giving me more and more things to think about. Isn't it more convenient for the developer to not have to think about these things...where I could trust the browser to match every selector as quickly as it can regardless of whether it is unnecessarily in an @defer rule?

It would be more convenient, yes.  I'm not sure it's best, is all.
Confusing bugs where a style updates slowly because you used a "slow"
selector aren't good.

~TJ

Received on Friday, 12 July 2013 19:19:52 UTC