[Bug]: Field validationMessage states using palette colors instead of state tokens

[mfishma]

Component

Field

Package version

9.58.0

React version

17

Environment

n/a

Current Behavior

When using <Field> validationMessage, where validationState is set to warning, error, or success, the colors being set to tokens like colorPaletteDarkOrangeForeground,, colorPaletteRedForeground1, colorPaletteRedBorder2, etc.
Since those tokens don't really change from theme to theme, it might be unexpected that these don't change like the MessageBar colors.

Expected Behavior

it should be using tokens like colorStatusDangerForeground1 or colorStatusSuccessForeground1 to color these statuses, to match the MessageBar color palette.

Reproduction

https://react.fluentui.dev/?path=/docs/components-field--docs#validation-message

Steps to reproduce

Go to https://react.fluentui.dev/?path=/docs/components-field--docs#validation-message - to the Validation Message section of the Field. Inspect the colors used, and see that they're not using status colors for the theme.
Comparing to https://react.fluentui.dev/?path=/docs/components-messagebar--docs#intent which uses the status colors.

Are you reporting an Accessibility issue?

no

Suggested severity

Low - Has or doesn't need a workaround

Products/sites affected

No response

Are you willing to submit a PR to fix?

no

Validations

• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[mainframev]

@mfishma

The values don't match the Figma specification. For example, for error status there is #BC2F32 color value used, meanwhile colorStatusDangerForeground1 is #B10E1C. From tokens perspective, it makes sense to have it as you wrote, to have status tokens instead of palette ones.

We have similar issue with other components, this should be discussed and solved in one bunch.

[mfishma]

I checked, looking at this Figma, and I don't see that, I see the UI kit is using the status-y tokens for Field and Badge.

[microsoft-github-policy-service]

This issue has not had activity for over 180 days! We're adding Soft close label and will close it soon for house-keeping purposes.
Still require assistance? Please add comment - "keep open".

[microsoft-github-policy-service]

Because this reported issue has not had any activity for over 180 days, we're automatically closing it for house-keeping reasons.

Still require assistance? Please, create a new issue with up-to date details and latest version of Fluent.