Merged
Conversation
See #16911 This will create a denser layout by default, enabling people to see more information on the page without having to discover the global settings menu. Signed-off-by: Julius Volz <julius.volz@gmail.com>
bboreham
approved these changes
Feb 3, 2026
Member
bboreham
left a comment
There was a problem hiding this comment.
Seems plausible to me.
Since the issue mentions LTS, do we need to consider a backport?
Member
Author
Good question. It wouldn't hurt, I think. It's not strictly a bugfix, but a change in default behavior that improves page display performance for people with a large number of firing alerts. |
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.
See #16911
This will create a denser layout by default, enabling people to see more information on the page without having to discover the global settings menu.
Which issue(s) does the PR fix:
Fixes #16911
Does this PR introduce a user-facing change?