- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Sep 2017 19:37:48 +0000
- To: public-css-archive@w3.org
It would require a reparse, yes. ---------- > How would this work for UA predefined constants? Would they be expected to have an @global rule in a stylesheet at UA precedence level, which gets updated if the value changes? The UA stylesheet is unobservable, so this doesn't matter. The only observable part would be the JS API, which would I suppose have readonly entries in the map that could be listened to for changes. > Also, I really think this concept should have a single name in syntax. Either @global+global() or @constant+constant(). @global defining the value read by constant() seems needlessly inconsistent. Oh, yes, certainly. All the discussion of "global variables" just led my fingers to type `@global`; whatever name we choose will definitely be used consistently between the definition and use. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/1817#issuecomment-330650505 using your GitHub account
Received on Tuesday, 19 September 2017 19:38:11 UTC