Skip to content

Design System: move fluent-next onto design tokens 262.10.1 - #34916

Open
EugeniyKiyashko wants to merge 2 commits into
DevExpress:feature/26_2_new_fluent_theme_with_design_tokensfrom
EugeniyKiyashko:fluent-next/update
Open

Design System: move fluent-next onto design tokens 262.10.1#34916
EugeniyKiyashko wants to merge 2 commits into
DevExpress:feature/26_2_new_fluent_theme_with_design_tokensfrom
EugeniyKiyashko:fluent-next/update

Conversation

@EugeniyKiyashko

Copy link
Copy Markdown
Contributor

No description provided.

262.8.0 renamed the whole semantic colour tier: surface/content/border with
palette + variant + state became a flat bg/content/border vocabulary, so 262.6.0
could not be bumped without remapping every role the theme reads.

All 102 semantic roles fluent-next consumes still exist under the new names —
each one was matched by its resolved value in both light and dark, not by its
spelling. 673 references across 65 stylesheets follow the package conventions:
subdued becomes subtle, deep becomes subtler (bg-low for neutral), compound
becomes shared, accessible becomes contrast, and the default variant loses its
segment. Flattening the compiled bundle and resolving every var() chain gives an
identical result for both modes, so no screenshot moves.

Registries regenerated: the package now defines 732 component tokens and adds
highlight, scrim and veil as parts.

(cherry picked from commit d7d3ccd385a9a0444466171d1fac6ee20cee455f)
@EugeniyKiyashko
EugeniyKiyashko requested review from a team as code owners August 25, 2026 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants