fix(compiler): handle case-sensitive CSS custom properties#41380
fix(compiler): handle case-sensitive CSS custom properties#41380crisbeto wants to merge 2 commits intoangular:masterfrom
Conversation
Currently we normalize all CSS property names in the `StylingBuilder` which breaks custom properties, because they're case-sensitive. These changes add a check so that custom properties aren't normalized. Fixes angular#41364.
AndrewKushnir
left a comment
There was a problem hiding this comment.
Thanks for the fix @crisbeto 👍 I've just left a few minor comments.
I've also noticed that you've applied "target: major" label, just curious if you see any potential risks with this change that might be worth mentioning in commit message or here in PR description?
Thank you.
|
Regarding the targeting, I was just confused whether targeting |
|
@crisbeto FYI presubmits are successful for the changes in this PR. I'm adding the "cleanup" label for now to see if you want to change the "target" label (if not, just remove the "cleanup" label). Thank you. |
…1380) Currently we normalize all CSS property names in the `StylingBuilder` which breaks custom properties, because they're case-sensitive. These changes add a check so that custom properties aren't normalized. Fixes angular#41364. PR Close angular#41380
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Currently we normalize all CSS property names in the
StylingBuilderwhich breaks custom properties, because they're case-sensitive. These changes add a check so that custom properties aren't normalized.Fixes #41364.