-
What color is this text in browsers… with var support / without var support? html { color: blue; color: var(--undefined); }Permalink On twitter.com
♻️ 6 Retweets ❤️ 9 Favorites Mood +4 🙂
-
This poll is holding steady, with correct "default/blue" ~20% 1. Invalid/unknown *declarations* can't be parsed, & are ignored—falling back to previous declarations 2. Invalid/undefined *variables* parse, but fail to compute later—falling back toOn twitter.com
unsetcodepen.io/mirisuzanne/pen/OYoVLX -
This behavior is defined in the spec (w3.org/TR/css-variables-1/#invalid-variables) because parsing-time & computed-value-time have different restrictions. But it also gives us the ability to handle 2 distinct fallback paths – one with var() support, and one without.Permalink On twitter.com
-
Parsed-but-not-computed values are kinda cool—likePermalink On twitter.com
nullin Sass, orundefinedin JS—for handling set/unset, as distinct from variable/non-variable. You can also make that explicit, usingunsetor any invalid value for your context. See line 41: codepen.io/mirisuzanne/pen/BEvjbm