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
What I mean is that when defining CSS variables, it is not necessary to write it in the elements' {}, which is equivalent to a syntactic sugar, and the variables are implicitly bound to the :root element.
For example, the following two codes will be equal:
No, this can never happen. Mixing properties and selectors at the same level is problematic - see the long discussion in #7834, where we have to do a lot of work to allow mixing properties with nested selectors.
In particular, the current solution in the spec for nested rules disallows starting a selector with an identifier (aka a tagname selector), which we definitely can't retroactively apply to all existing CSS. ^_^
What I mean is that when defining CSS variables, it is not necessary to write it in the elements'
{}
, which is equivalent to a syntactic sugar, and the variables are implicitly bound to the:root
element.For example, the following two codes will be equal:
The text was updated successfully, but these errors were encountered: