Repository navigation
Conversation
✅ Successfully generated changelog entry!Entry generated via PR titleTo modify this entry, edit PR title using proper format. 📋Changelog Preview🐛 Fixes
|
This branch has not been 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.
Summary
Currently, Blueprint’s generated CSS repeats resolved color values instead of preserving the relationships defined by the token source. For example, both
--bp-palette-blue-3and--bp-intent-primary-restcontain#2d72d2, even though the intent token is defined as an alias of the palette token.This change preserves those relationships by emitting ordinary aliases as CSS var() references. This keeps the generated CSS aligned with the token source and allows palette overrides to flow through the intent and semantic tokens that depend on them. Colors derived using relative color syntax still retain literal fallbacks for older browsers.
Generated CSS
Before:
After:
Value-only diff (declaration order omitted)
--bp-surface-layer-color-primarydeliberately stays literal because it applies opacity to another token and older browsers need the fallback.--bp-surface-layer-primarycan reference it directly; browsers that support relative colors will pick up the relative-color value.Full compiled CSS
The compiled design-token stylesheet is not checked in, so the full output is included below.
Before
After
Reviewer notes
The default values are unchanged, so this should not look different. Even so, please inspect the generated styles in light and dark modes for regressions, especially intent states, focus treatments, and layered surfaces.