Polish Settings window chrome and category responsiveness - #285
Closed
Yankj wants to merge 7 commits into
Closed
Conversation
Author
Author
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
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.

Why
During repeated use of Settings, I noticed several issues that made this high-frequency macOS surface feel slower and less native than the rest of the app:
These issues were especially noticeable because Settings is where users repeatedly compare options and expect immediate navigation feedback.
What changed
Native window chrome and sidebar
windowBackgroundColor, with a.sidebarmaterial that follows active/inactive window state.Responsive category switching
Regression coverage
Validation
IslandBridgeE2ETestsandSocketServerTestsare excluded, matching CI).PingIslandTestssuite passed.arm64andx86_64.