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
There are false negatives for CSS Variables that span multiple parameters in alpha-value-notation, e.g.
a { color:hsl(var(--hsl) /50%) }
As an aside, this makes me realise how CSS Variables make static analysis less comprehensive. In the past, we were confident that our rules would catch everything, but with CSS Variables that is no longer the case. CSS Variables muddy the waters every time we use the value parser to find (see the find* utilities) a particular value, e.g. a font-size within the font shorthand property or an <alpha-value> within a colour function. A CSS Variable value is only known at runtime when the browser resolves it based on the cascade and DOM.
The best we can do is narrow down the possibilities of what a particular node could represent.
Which rule, if any, is the bug related to?
alpha-value-notation
What code is needed to reproduce the bug?
a { color:hsl(var(--hsl) /0.5) }
What stylelint configuration is needed to reproduce the bug?
There are false negatives for CSS Variables that span multiple parameters in
alpha-value-notation
, e.g.As an aside, this makes me realise how CSS Variables make static analysis less comprehensive. In the past, we were confident that our rules would catch everything, but with CSS Variables that is no longer the case. CSS Variables muddy the waters every time we use the value parser to find (see the
find*
utilities) a particular value, e.g. a font-size within thefont
shorthand property or an<alpha-value>
within a colour function. A CSS Variable value is only known at runtime when the browser resolves it based on the cascade and DOM.The best we can do is narrow down the possibilities of what a particular node could represent.
alpha-value-notation
13.9.0
API via Demo
No.
The following warnings to be flagged:
No warnings.
The text was updated successfully, but these errors were encountered: