W3C home > Mailing lists > Public > www-style@w3.org > July 2013

RE: [selector-profiles] confusion

From: François REMY <francois.remy.dev@outlook.com>
Date: Thu, 11 Jul 2013 18:17:35 +0200
Message-ID: <DUB120-W17FE7B278D2A45983486C6A57B0@phx.gbl>
To: Sylvain Galineau <galineau@adobe.com>
CC: "lea@w3.org" <lea@w3.org>, "www-style@w3.org" <www-style@w3.org>
>>> 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... 		 	   		  
Received on Thursday, 11 July 2013 16:18:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:32 UTC