-
Notifications
You must be signed in to change notification settings - Fork 14.1k
Reduce UI footprint for compression events #23910
Copy link
Copy link
Closed as not planned
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalityeffort/small1 day or less: trivial logic, UI adjustments, docs1 day or less: trivial logic, UI adjustments, docskind/customer-issueIssues that were reported by customersIssues that were reported by customerspriority/p1Important and should be addressed in the near term.Important and should be addressed in the near term.status/bot-triagedtype/feature🔒 maintainer only⛔ Do not contribute. Internal roadmap item.⛔ Do not contribute. Internal roadmap item.
Metadata
Metadata
Assignees
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalityeffort/small1 day or less: trivial logic, UI adjustments, docs1 day or less: trivial logic, UI adjustments, docskind/customer-issueIssues that were reported by customersIssues that were reported by customerspriority/p1Important and should be addressed in the near term.Important and should be addressed in the near term.status/bot-triagedtype/feature🔒 maintainer only⛔ Do not contribute. Internal roadmap item.⛔ Do not contribute. Internal roadmap item.
Type
Fields
Give feedbackNo fields configured for issues without a type.
What would you like to be added?
Reduce the impact of more compression events, by reducing the UI footprint when this happens.
Why is this needed?
As compression happens more frequently (at 20% threshold), it should be less disruptive to the user experience.
Additional context