RE: [selector-profiles] confusion

On Jul 11, 2013 12:19 PM, "François REMY" <francois.remy.dev@outlook.com>
wrote:
>
> >>> Or there could just be a @static rule,
> >>> with everything inside running statically,
> >>> including fast selectors. Just an idea.
> >>
> >>What do you actually mean by 'running statically'? Being executed only
> >>once at the page load? If the page takes a while to load, which is
> >>commonly the case on mobile phones & cellular connections, your style
may
> >>even never get applied using that strategy.
> >
> > If something runs once the page loads, why wouldn't it run if the load
is
> > slow? It'd never get applied if the load never completes but that'd be
> > true whether the UA runs on a mobile device or a desktop.
>
> Well, I just meant that some pages just never execute the load event on
mobile phones because they actually never stop loading in a reasonable
timeframe (ie: the user navigate away before the page finished loading). Of
course if you let your phone download the page without interacting with it,
the event will eventually fire at some point.
>
> Anyway, I do think that selectors that are evaluated only once will be a
pain for developers. It would be very hard to debug them, or even report
them in debug tools. This is not to say it's impossible, but that would be
messy...

I don't really love the static idea personally,  but IIRC selectivizr and
some other things worked that way and people still found value.  It's fine
I suppose to not have them in CSS natively if that is what is necessary -
it just stinks that we know it will get done anyway and it will be slower
than the slow native alternative