Repository navigation
metrics tree scroll issue fixed - #20758
Merged
James Newton-King (JamesNK) merged 1 commit intoOct 6, 2026
Merged
Conversation
Siri (heyysiri)
requested review from
James Newton-King (JamesNK) and
Adam Ratzman (adamint)
as code owners
October 6, 2026 07:19
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 20758Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 20758" |
James Newton-King (JamesNK)
approved these changes
Oct 6, 2026
Member
|
Thanks! Will try to get this fix out ASAP |
Member
|
/backport to release/13.6 |
Contributor
|
Started backporting to |
James Newton-King (JamesNK)
enabled auto-merge (squash)
October 6, 2026 14:12
Jose Perez Rodriguez (joperezr)
pushed a commit
that referenced
this pull request
Oct 6, 2026
Backport of #20758 to release/13.6 /cc @JamesNK @heyysiri ## Customer Impact In Aspire 13.6, the Metrics page's meter/instrument tree cannot be scrolled when it exceeds the viewport, preventing customers from reaching and selecting metrics below the fold. ## Testing Manually verified in Brave that the pane does not scroll before the change and that mouse-wheel scrolling reveals lower meters after the change. No automated test was added because existing dashboard tests do not validate visual layout. ## Risk Low. This is a localized CSS change that applies the chart pane's existing `overflow: auto` behavior to the metrics tree pane. ## Regression? Yes — introduced by the Fluent UI Blazor v5 migration in #19431. Co-authored-by: heyysiri <siriraj2004@gmail.com>
This was referenced Oct 7, 2026
This was referenced Oct 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Problem
On the Metrics page, the left-hand meter/instrument tree can't be scrolled when it's taller than the window. There's no scrollbar and the mouse wheel does nothing, so instruments below the fold can't be reached.
This regressed when the dashboard moved to Fluent UI Blazor v5 in #19431. The v4
FluentSplittergave each panel its own scroll container. The v5FluentMultiSplitterPanedoesn't. The chart pane already gotoverflow: autoin that migration, but the tree pane didn't.Change
In
Metrics.razor.css, the existingoverflow: autorule for the chart pane now also applies to the pane that contains the metric tree (.metrics-tree).Verification
overflow: hidden; a mouse-wheel scroll leaves it at the top.Fixes #20728
Checklist