Extended Tokens: Input - #34796
Conversation
|
Looks like both pressed (active) and selected (focus-within) states use the same color for the colored bottom border bar, but they should have alternate states based on original spec, let's review those and ensure that pressed takes priority and has it's legacy color enabled (+ pressed semantic token) |
Mitch-At-Work
left a comment
There was a problem hiding this comment.
Some minor tweaks required on the bottom bar
Updated border Can you clarify on this? I'll reach out. Thanks! Mitch-At-Work
|
|
Pull request demo site: URL |
9bea44f to
3e58442
Compare
54c547a
into
microsoft:extended-tokens
Co-authored-by: Mitch-At-Work <mifraser@microsoft.com>
Co-authored-by: Mitch-At-Work <mifraser@microsoft.com>


This pull request introduces updates to the
@fluentui/react-inputpackage, focusing on replacing hardcodedtokenswithsemanticTokensfor styling consistency and adding new semantic token definitions. These changes aim to improve maintainability and alignment with design specifications.Updates to
@fluentui/react-inputstyling:tokenswithsemanticTokensinuseInputStyles.styles.tsfor properties likeborderRadius,backgroundColor,borderColor, andcolor, ensuring a more consistent and semantic approach to styling. [1] [2] [3] [4] [5] [6] [7] [8] [9]Dependency and token updates:
@fluentui/semantic-tokensas a dependency inpackage.jsonto support the use of semantic tokens.foregroundCtrlIconOnNeutralRestinsemantic-tokensand updated its fallback value to includecolorNeutralForeground3. [1] [2] [3]Changelog:
@fluentui/react-inputpackage to document the minor update and its impact on dependent packages.