-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Polish sidebar extensions and titlebar chrome #5017
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
d25e768
Tighten sidebar titlebar control width
azooz2003-bit be98620
Reduce sidebar titlebar minimum width
azooz2003-bit 71f72e3
Harden sidebar extension surface creation
azooz2003-bit 14c5900
Polish sidebar extension narrow states
azooz2003-bit 94d8e66
Tighten sidebar titlebar minimum width
azooz2003-bit 85cba8b
Fix sidebar extension CI issues
azooz2003-bit b233580
Tighten sidebar extension permissions and UX
azooz2003-bit e87c66a
Restore titlebar accessory layout
azooz2003-bit eeecf66
Restore pre-extension titlebar controls
azooz2003-bit fddb559
Restore titlebar text with sidebar visible
azooz2003-bit bc03c07
Fix sidebar visibility change warning
azooz2003-bit a44945b
Keep titlebar accessory next to traffic lights
azooz2003-bit 019b269
Keep workspace titlebar over panes
azooz2003-bit 30f248c
Harden reload build artifact handling
azooz2003-bit 2562d72
Keep workspace titlebar anchored to window
azooz2003-bit 6a68659
Align workspace titlebar after traffic lights
azooz2003-bit b0af2f9
Keep workspace title right of sidebar
azooz2003-bit 09648c1
Make workspace titlebar a root chrome layer
azooz2003-bit 99d57bf
Scope workspace titlebar overlay to chrome band
azooz2003-bit File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
visibleContentWidthis computed twice perupdateSize()call — once insidecontentSize(config:)(which callsvisibleContentWidthinternally) and once again as a separate local. Since this is not a hot path the impact is negligible, but the redundancy is easy to eliminate by computingvisibleContentWidthfirst and threading it intocontentSize.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!