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
Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
If i define a css var with the value of a css var like in the code snippet below some material css variables are not defined correctly.
E.g. --mdc-linear-progress-track-color is set to var(--primary-500) but should be converted to a rgba color with 0,25 opacity.
Upvote, I experienced this today when updating to material v16 as well. Really annoying in combination with #26056 (comment), because of this bug I have to hard copy values out of my custom palette in order to fix the aforementioned bug. Workaround inception which gets really hard to maintain.
Palettes based on CSS variables were never supported, see #25981 (comment). Instead of creating a palette with CSS variables that are initialized to colors, you can pass those colors directly to the palette and it'll create variables for you. This specific case can also be worked around with .mdc-linear-progress__buffer-bar { opacity: 0.25 }, but there's no guarantee other places won't have a similar issue.
Is this a regression?
The previous version in which this bug was not present was
No response
Description
If i define a css var with the value of a css var like in the code snippet below some material css variables are not defined correctly.
E.g. --mdc-linear-progress-track-color is set to
var(--primary-500)
but should be converted to a rgba color with 0,25 opacity.That causes the theme to have some bad behaviour.
`:root{
--primary-500: #FF0000
}
$primary:(
500: var(--primary-500)
)
`
Reproduction
StackBlitz link: https://stackblitz.com/edit/stackblitz-starters-d9ccxk
Expected Behavior
The css var should be handled like a hex value
Actual Behavior
The css var is copied
Environment
The text was updated successfully, but these errors were encountered: