You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduces a new function which essentially does the same thing as var()
Lacks a clear specificity on how var() plays with env()
Adds another level of complexity to CSS for new learners which may impede or slow down learning
Instead, I propose using the familiar var keyword already available. UAs can predefine custom properties to known variable names. It seems to me that the draft tries to solve a problem that really isn't there for most authors.
For fallbacks, the author may define those using the normal :root or specificity.
Instead of focusing on creating a new function, let's focus on a naming convention for UAs to follow that standardizes the variable names we can use.
The text was updated successfully, but these errors were encountered:
After reading the proposal spec on CSS environment variables, I find the proposed
env
keyword redundant and misleading:var()
var()
plays withenv()
Instead, I propose using the familiar
var
keyword already available. UAs can predefine custom properties to known variable names. It seems to me that the draft tries to solve a problem that really isn't there for most authors.For fallbacks, the author may define those using the normal
:root
or specificity.Instead of focusing on creating a new function, let's focus on a naming convention for UAs to follow that standardizes the variable names we can use.
The text was updated successfully, but these errors were encountered: