microsoft / microsoft/fluentui

[Bug]: Selected NavSubItem shows no indicator inside expanded NavCategory

Open
#36,754 2 comments 0 reactions 1 assignee View on GitHub

@mainframev is already working on this.

Since Sep 17, 2026.

Component: Nav Fluent UI react-components (v9) Type: Bug :bug:
Dominant language
TypeScript
Stars
20.3k
Forks
2.9k
Avg merge
2d 9h
Merged PRs (30d)
46

Description

Component

Nav (Preview)

Package version

9.74.7

React version

19.3.0

Environment
System:
  OS: Windows 11 10.0.26200
  CPU: (20) x64 Intel(R) Core(TM) Ultra 7 265HX
  Memory: 8.44 GB / 31.68 GB
Browsers:
  Edge: Chromium (152.0.4191.53)
npmPackages:
  @fluentui/react-components: ^9.74.7 => 9.74.7 
  @fluentui/react-icons: ^2.0.339 => 2.0.340 
  @types/react: ^19.2.18 => 19.3.0 
  @types/react-dom: ^19.2.4 => 19.3.0 
  react: ^19.2.8 => 19.3.0 
  react-dom: ^19.2.8 => 19.3.0
Current Behavior

When a NavSubItem inside an expanded NavCategory is selected (selectedValue matches its value), its selection indicator is not visible.

Image

The indicator pseudo-element (::after) is positioned with inset-inline-start: 46px and margin-inline-start: -52px, i.e. 6 px outside the item's box.

Expected Behavior

A selected NavSubItem shows its selection indicator while its category is expanded, aligned with the indicators of top-level NavItems.

Image
Reproduction

https://stackblitz.com/edit/drvr8jcg?file=src%2Fexample.tsx

Steps to reproduce
  1. Open "Job Postings"
  2. Click on "Openings"
Are you reporting an Accessibility issue?

No response

Suggested severity

Medium - Has 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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.