microsoft / microsoft/fluentui
Dropdown filled-darker has no visible resting boundary in Teams High Contrast theme
@bsunderhus is already working on this.
Since Aug 27, 2026.
- Dominant language
- TypeScript
- Stars
- 20.3k
- Forks
- 2.9k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 46
Description
Component
Dropdown
Package version
9.74.7
React version
Not app-specific; reproduced in the public Fluent UI React v9 Storybook documentation.
Environment
Reproduced in the public Fluent UI React v9 Storybook documentation with the high contrast theme enabled.
Browser/OS are not expected to be specific to the issue because the repro is visible in the published docs styling.
Current Behavior
Dropdown controls using appearance="filled-darker" do not have a visible resting boundary in the high contrast theme.
This appears to differ from other filled controls such as Input and Textarea, which use tokens.colorTransparentStroke so the resting boundary becomes visible in high contrast. Dropdown currently appears to use transparent instead:
https://github.com/microsoft/fluentui/blob/master/packages/react-components/react-combobox/library/src/components/Dropdown/useDropdownStyles.styles.ts#L178C1-L179C1
Expected Behavior
A filled-darker Dropdown should have a visible resting boundary in high contrast, consistent with other filled controls.
Reproduction
Steps to reproduce
- Open the Fluent UI React v9 Dropdown docs reproduction link.
- Ensure the high contrast theme is enabled in Storybook.
- Find a
Dropdownexample usingappearance="filled-darker". - Observe that the Dropdown has no visible resting outline/border.
Are you reporting an Accessibility issue?
yes
Suggested severity
Medium - Has workaround
Products/sites affected
Downstream products/sites using Fluent UI React v9 Dropdown with appearance="filled-darker" in high contrast themes.
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.