fix(ui): use defined status and interaction color tokens - #8012
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Several product status indicators referenced undefined CSS variables, leaving attention dots and progress fills transparent and warning/action text without its intended color.
Use the existing
--brand-bluefor progress and attention,--warningfor the legacy-snapshot warning, and--selectionfor the download action and Cursor keyboard focus ring. Apply the unviewed-download color to its icon instead of overriding the Button. Layout, dimensions, and interactions remain unchanged.Validation: all eight stale references removed by a tracked-source search; the external conformance audit removes all seven associated consumer findings with no new findings. Existing EMCN and browser-download tests, workspace type/lint checks, import resolution, and mandatory API validation pass. A browser fixture compiled from the real application CSS verifies both themes, matching dimensions, and keyboard focus colors; full live product flows were not exercised. Audit tools and visual-review files are kept outside this PR.