Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(multiple): derive all token values from theme #28664

Merged
merged 1 commit into from Feb 29, 2024

Conversation

crisbeto
Copy link
Member

During the transition to tokens, we ended up with a bunch of places with hardcoded values in the form of if($is-dark, #fff, #000). This is problematic for custom palettes, because the value is always hardcoded.

These changes attempt to derive the same values from the palette directly.

Fixes #26056.

@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release labels Feb 29, 2024
@crisbeto crisbeto force-pushed the theming-fixes branch 6 times, most recently from 27bb88e to 499289a Compare February 29, 2024 17:21
During the transition to tokens, we ended up with a bunch of places with hardcoded values in the form of `if($is-dark, #fff, #000)`. This is problematic for custom palettes, because the value is always hardcoded.

These changes attempt to derive the same values from the palette directly.

Fixes angular#26056.
@crisbeto crisbeto self-assigned this Feb 29, 2024
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Feb 29, 2024
@crisbeto crisbeto merged commit cfdfa9a into angular:main Feb 29, 2024
27 checks passed
crisbeto added a commit that referenced this pull request Feb 29, 2024
During the transition to tokens, we ended up with a bunch of places with hardcoded values in the form of `if($is-dark, #fff, #000)`. This is problematic for custom palettes, because the value is always hardcoded.

These changes attempt to derive the same values from the palette directly.

Fixes #26056.

(cherry picked from commit cfdfa9a)
@crisbeto crisbeto mentioned this pull request Mar 4, 2024
crisbeto added a commit to crisbeto/material2 that referenced this pull request Mar 13, 2024
The changes from angular#28664 appear to have caused ripples to be solid in some setups. These changes add a fallback to the old behavior if that's the case.

Fixes angular#28706.
crisbeto added a commit that referenced this pull request Mar 13, 2024
The changes from #28664 appear to have caused ripples to be solid in some setups. These changes add a fallback to the old behavior if that's the case.

Fixes #28706.
crisbeto added a commit that referenced this pull request Mar 13, 2024
The changes from #28664 appear to have caused ripples to be solid in some setups. These changes add a fallback to the old behavior if that's the case.

Fixes #28706.

(cherry picked from commit 438ff93)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(button): Palette contrast values are not applied
2 participants