Repository navigation
Migrate to Fluent UI Blazor v5 (umbrella: plan, then split) #81
Description
This was generated by AI during triage.
What to build
Migrate the Web project from Microsoft.FluentUI.AspNetCore.Components 4.x to 5.x. Dependabot opened #71 and #72 for the 5.0.0 bump; the CI on #71 is red because v5 is a breaking release, so this is a planned migration, not a version bump.
Migration guide: https://v5.fluentui-blazor.net/Migration
Needs before it is ready for an agent
- A planning pass over the guide: list every breaking change that touches our pages, dialogs, services and CSS (the Event dialog scroll-box gutter fix from Fix horizontal scrollbar(s) #24 is one place to recheck).
- A decision on timing. It touches every page, so it conflicts with any UI feature work running at the same time. It should run alone.
- Split into tickets from that pass (this issue is the umbrella, not the work).
Acceptance criteria
- Planning pass done and tickets filed
- Web project builds on 5.x with 0 errors and 0 warnings
- Every page and dialog verified on a running instance
- chore: Bump Microsoft.FluentUI.AspNetCore.Components from 4.14.4 to 5.0.0 #71 and chore: Bump Microsoft.FluentUI.AspNetCore.Components.Icons from 4.14.4 to 5.0.0 #72 closed by the migration PR(s)
Out of scope
Behaviour changes unrelated to the upgrade.
Activity
mwg-bender commentedon Oct 7, 2026
Note from #107: the Fluent UI v4 select race (
ArgumentNullException ... jsObjectReferencewhen a key is pressed before the select's JS module loads) is deferred to this migration. v5.0.0 source no longer has the C# keydown path, so it may disappear. Add a re-test of the early-Tab and Escape-before-load flows on/activities(see #107) to the migration's acceptance checks.