Skip to content

[release/13.6] metrics tree scroll issue fixed - #20762

Merged
Jose Perez Rodriguez (joperezr) merged 1 commit into
release/13.6from
backport/pr-20758-to-release/13.6
Oct 6, 2026
Merged

Jose Perez Rodriguez (joperezr) merged 1 commit into
release/13.6from
backport/pr-20758-to-release/13.6

Conversation

@aspire-repo-bot

@aspire-repo-bot aspire-repo-bot Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

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: auto behavior to the metrics tree pane.

Regression?

Yes — introduced by the Fluent UI Blazor v5 migration in #19431.

@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 20762

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 20762"

@JamesNK James Newton-King (JamesNK) added the Servicing-consider Issue for next servicing release review label Oct 6, 2026
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Tests selector

13 / 99 PR test projects · 2 PR jobs, from 1 changed file.

Selected PR test projects (13 / 99)

Aspire.Dashboard.Components.Tests, Aspire.Dashboard.Tests, Aspire.Hosting.Azure.Kubernetes.Tests, Aspire.Hosting.Azure.Tests, Aspire.Hosting.Blazor.Tests, Aspire.Hosting.Dotnet.Tests, Aspire.Hosting.DotnetTool.Tests, Aspire.Hosting.JavaScript.Tests, Aspire.Hosting.Radius.Tests, Aspire.Hosting.Testing.Tests, Aspire.Hosting.Tests, Aspire.Playground.Tests, Aspire.Templates.Tests

Selected PR jobs (2)

extension-e2e, native-dashboard-validation


How these were chosen — grouped by what changed

⚠️ 12 of the 13 selected test projects come from a single change — src/Aspire.Dashboard/Components/Pages/Metrics.razor.css.

🔧 src/Aspire.Dashboard/Components/Pages/Metrics.razor.css (changed source)
→ 12 via the project graph: Aspire.Dashboard.Components.Tests, Aspire.Dashboard.Tests, Aspire.Hosting.Azure.Kubernetes.Tests (3 hops), Aspire.Hosting.Azure.Tests (2 hops), Aspire.Hosting.Blazor.Tests (2 hops), Aspire.Hosting.Dotnet.Tests (2 hops), Aspire.Hosting.DotnetTool.Tests (2 hops), Aspire.Hosting.JavaScript.Tests, Aspire.Hosting.Radius.Tests (2 hops), Aspire.Hosting.Testing.Tests, Aspire.Hosting.Tests, Aspire.Playground.Tests (2 hops)

📦 affected project Aspire.Dashboard
→ 1 test: Aspire.Templates.Tests

Job reasons

Job Triggered by
extension-e2e • src/Aspire.Dashboard/Components/Pages/Metrics.razor.css
• affected project Aspire.Dashboard
native-dashboard-validation affected project Aspire.Dashboard

Selection computed for commit a0f4d81.

@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

@joperezr
Jose Perez Rodriguez (joperezr) merged commit 660f92c into release/13.6 Oct 6, 2026
449 of 459 checks passed
@aspire-repo-bot

Copy link
Copy Markdown
Contributor Author

✅ No documentation update needed.

Step 5 branch taken: "excluded → backport" (exclusion_reasons: base_branch_is_release, head_branch_is_backport, title_release_prefix, body_backport_marker)

Triggered signals: none (signal_count: 0); the docs-required gate was never evaluated because excluded == true overrides it.

Evidence for exclusion:

  • PR title is prefixed [release/13.6].
  • PR body states "Backport of metrics tree scroll issue fixed #20758 to release/13.6" (explicit backport marker).
  • Base ref is release/13.6 (a release branch), consistent with a backport.
  • Head branch matches the bot's backport branch naming convention.

This PR is a backport of #20758 (a CSS-only fix restoring overflow: auto scrolling on the Metrics page's meter/instrument tree pane). Per workflow policy, documentation for backports is authored against the original forward PR on the default branch, not duplicated here. No docs PR drafted.

This was referenced Oct 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-dashboard Servicing-consider Issue for next servicing release review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants