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
If I am not mistaken, mix() is valid for custom properties, whose initial value is the guaranteed-invalid value, ie. an omitted value.
A mix() notation is invalid if either of its <declaration-value>s are invalid when interpreted as a whole value for the property the function is used in, or if the property using it is not animatable.
Should mix() syntax allow omitting <declaration-value> ...
Yes, passing a space does indeed satisfy <declaration-value>, but I should indeed go ahead and give it ? since that's also a valid custom property value.
If I am not mistaken,
mix()
is valid for custom properties, whose initial value is the guaranteed-invalid value, ie. an omitted value.Should
mix()
syntax allow omitting<declaration-value>
...... to accept inputs like
--custom: mix(50%; ; on)
?The text was updated successfully, but these errors were encountered: