W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2016

[csswg-drafts] [mediaqueries][mediaqueries-4][mediaqueries-5] should 'initial-only' have an explicit minimum threshold?

From: Tantek Çelik via GitHub <sysbot+gh@w3.org>
Date: Tue, 20 Sep 2016 13:57:34 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-178067415-1474379852-sysbot+gh@w3.org>
tantek has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== [mediaqueries][mediaqueries-4][mediaqueries-5] should 
'initial-only' have an explicit minimum threshold? ==
https://drafts.csswg.org/mediaqueries/#scripting

Formerly "Issue 4" inline in the spec, brought here to capture and 
discuss:

"
Should there be an explicit minimum threshold to meet before a UA is 
allowed to claim initial-only? Having one would mean authors would 
know what they can depend on, and could tailor their scripts 
accordingly. On the other hand, pinpointing that threshold is 
difficult: if it is set too low, the scripting facilities that authors
 can depend on may be to constrained to be practical, even though 
actual UAs may potentially all support significantly more. But trying 
to set it higher may cause us to exclude UAs that do support scripting
 at loading time, but restrict it in some cases based on complex 
heuristics. For instance, conservative definitions likely include at 
least running all inline scripts and firing the DOMContentLoaded 
event. But it does not seem useful for authors to constrain themselves
 to this if most (or maybe all) initial-only UAs also load external 
scripts (including async and defer) and fire the load event. On the 
other hand, requiring external scripts to be loaded and the load event
 to be fired could exclude UAs like Opera mini, which typically do run
 them, but may decide not to based on timeouts and other heuristics.
"

Feel free to adjust issue name/title and "[...]" labels according to 
where this feature ends up. Thanks!

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/503 using your GitHub 
account
Received on Tuesday, 20 September 2016 13:57:41 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:34 UTC