RE: [selector-profiles] confusion

> Dude, I got all that. I am asking for the specific use-cases that suggest
> that, yes, authors might indeed end up calling qSA on load so regularly it
> ought to be baked in. Having 'a' use-case or 'some' use-cases is very
> different from 'yes, this sounds like something I'd want to do regularly'.

Actually, you may want to ask Lea for examples. I was dubious about that as well previously, particularly on the subject selector thing, but she did send me some pretty good use-cases over time. Sadly, that was mostly Twitter discussions so I don't have them handy right now.

The one I could think of however is:

   !label /for/ input:focus {
      ... focus style for the labels of the focused input ...
   }

This is only working on the complete profile right now for multiple reasons but authors can accept that the styling of the label may be a bit delayed after the focus change, that's not a big deal.




>>My proposal copes with all traditional stylesheets needs that can
>>accomodate slight FOUC {for example highlighting an element based on its
>>content as the user is typing for example...}
>
> Whoa. 'traditional stylesheets that can accommodate slight FOUC' could
> well be the weirdest, most subjective, undefinable thing I've ever read on
> this list. Respect…:)

That's because it's indeed an undefinable concept. Depending on context, an author may decide that some rules are not worth being kept up-to-date at every frame because this is costly and the delay that may result from not keeping them up-to-date does not affect the user experience in a critical way. So, yes, that's totally subjective. It depends on the use case, on the author vision, on the expected performance of the user's devices, and on the users expectations. But the author opting-out of full-time rule rematching has control and/or insight over those parameters.

Received on Thursday, 11 July 2013 19:07:45 UTC