-
-
Notifications
You must be signed in to change notification settings - Fork 150
Use sensible first-float window sizing #1073
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
wieslawsoltes
merged 3 commits into
wieslawsoltes:master
from
danwalmsley:codex/fixes/first-float-window-size
Mar 12, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
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.
The new
ResolveFloatingSizethreshold treats any tracked size<= 32as uninitialized, soFloatDockable/FloatAllDockablesnow overwrite legitimate small persisted dimensions every time a dockable is floated again. In practice, if a user intentionally resizes a floating tool/document window to something narrow (for example 24px) and later docks then re-floats it, this code forces owner/default sizing instead of restoring the saved size, which is a regression from the previousNaN-only fallback behavior.Useful? React with 👍 / 👎.
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.
Addressed in
926f6bd0.I narrowed the heuristic so we only treat clearly bogus initial tracked sizes as uninitialized by dropping the cutoff from
32to16. That preserves legitimate small persisted float sizes like24x24while still fixing the first-float tiny-window case.I also added a regression test covering the preserved-small-size case:
FloatDockable_PreservesSmallTrackedDocumentBoundsAboveTinyThresholdAnd re-ran the focused sizing tests.