Skip to content

[dev-v5][NavCategory] Fix font-family and sizing#4856

Merged
dvoituron merged 1 commit into
microsoft:dev-v5from
MarvinKlein1508:fix-navcategory-font
May 12, 2026
Merged

[dev-v5][NavCategory] Fix font-family and sizing#4856
dvoituron merged 1 commit into
microsoft:dev-v5from
MarvinKlein1508:fix-navcategory-font

Conversation

@MarvinKlein1508
Copy link
Copy Markdown
Collaborator

Pull Request

📖 Description

This PR inherits the font from FluentNav for FluentNavCategory. Previously categories were using a different fon-family and font-size.

Before:

before

After:

after

The effect was even stronger on mobile devices.

Before:

before_mobile

After:

after_mobile

✅ Checklist

General

  • I have added tests for my changes.
  • I have tested my changes.
  • I have updated the project documentation to reflect my changes.
  • I have read the CONTRIBUTING documentation and followed the standards for this project.

Component-specific

  • I have added a new component
  • I have added Unit Tests for my new component
  • I have modified an existing component
  • I have validated the Unit Tests for an existing component

⏭ Next Steps

Copilot AI review requested due to automatic review settings May 12, 2026 12:21
@MarvinKlein1508 MarvinKlein1508 modified the milestone: v5.0-RC3 May 12, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request fixes a visual inconsistency in the Nav component set by ensuring FluentNavCategory uses the same font-family and font-size as its surrounding FluentNav content (notably important because the category renders as a native <button>, which can otherwise use UA-default font styling).

Changes:

  • Update FluentNavCategory styling so .fluent-navcategoryitem inherits font-size and font-family.

@dvoituron dvoituron merged commit aa7a03a into microsoft:dev-v5 May 12, 2026
7 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants