feat(tokens): update tokens usage to reflect UI arquictecture #30676
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number: internal
What is the new behavior?
This pull request updates the color and background tokens throughout the Ionic component styles to use new design system variables, moving away from legacy primitives. The changes ensure a more consistent look and easier future theming by referencing centralized tokens for text color and background surfaces. Most components now use
globals.$ion-text-defaultfor text color andglobals.$ion-bg-surface-defaultfor backgrounds.Design Token Migration
globals.$ion-text-defaultinstead ofglobals.$ion-primitives-neutral-1200. This affects styles for buttons, cards, inputs, labels, toggles, radio buttons, chips, and more. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]globals.$ion-bg-surface-defaultinstead ofglobals.$ion-primitives-base-whitefor cards, items, inputs, radio buttons, toggles, chips, segments, toolbars, and more. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]Global Styles and Defaults
core.ionic.scsstoglobals.$ion-bg-surface-default, ensuring unified appearance.globals.$ion-text-defaultif--ion-text-coloris not set, improving fallback behavior.Component-Specific Adjustments
Does this introduce a breaking change?
Other information