- From: Brian Kardell <bkardell@gmail.com>
- Date: Wed, 10 Jul 2013 10:16:33 -0400
- To: François REMY <francois.remy.dev@outlook.com>
- Cc: www-style@w3.org
Received on Wednesday, 10 July 2013 14:17:05 UTC
On Jul 10, 2013 9:58 AM, "François REMY" <francois.remy.dev@outlook.com> wrote: > > > Is the recommendation to explicitly not > > support the complete profile in sheets? > > I keep hearing it sort of presented that > > way and i find the names a little > > confusing - they make it sound like > > nothing more than "these selectors are > > slower"... > > It would probably be a nice idea to name them in function of what they can do, indeed. It’s true that in the case of static selectors, most of the selectors in the “slow” profile will not be much slower than the others, it’s more the fact that keeping them up-to-date is costly. > > What about “Live Selectors” and “Static Selectors” (the former being selectors you can actually use in your stylesheets since they can live-update, and the latter being the ones that you can only use in qS/qSA-like use-cases)? It seems to me that initial/progressive matching is the big problem... It's not actually that difficult or even super expensive to match post update, right? Is it feasible to break them down that way? "You may experience fouc with these, they don't run until post complete"?
Received on Wednesday, 10 July 2013 14:17:05 UTC