Repository navigation
[release/13.6] metrics tree scroll issue fixed - #20762
Jose Perez Rodriguez (joperezr) merged 1 commit into
Conversation
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 20762Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 20762" |
Tests selector13 / 99 PR test projects · 2 PR jobs, from 1 changed file. Selected PR test projects (13 / 99)
Selected PR jobs (2)
How these were chosen — grouped by what changed
🔧 📦 affected project Job reasons
Selection computed for commit |
|
Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt. |
|
Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt. |
660f92c
into
release/13.6
|
✅ No documentation update needed. Step 5 branch taken: "excluded → backport" (exclusion_reasons: Triggered signals: none ( Evidence for exclusion:
This PR is a backport of #20758 (a CSS-only fix restoring |
Backport of #20758 to release/13.6
/cc James Newton-King (@JamesNK) Siri (@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: autobehavior to the metrics tree pane.Regression?
Yes — introduced by the Fluent UI Blazor v5 migration in #19431.