forked from Cloud-Pipelines/pipeline-editor
-
Notifications
You must be signed in to change notification settings - Fork 16
fix: Pipeline Details Docked Window Too Small #2676
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
camielvs
merged 1 commit into
master
from
08-27-fix_pipeline_details_docked_window_too_small
Sep 4, 2026
+133
−9
Merged
Changes from all commits
Commits
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.
This will reset ALL saved states across users, are we sure we want to do this?
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.
Fair thing to double-check — and on that line alone you would be right. What makes it safe is that the same change adds a migration step, so existing layouts get carried forward instead of thrown away. Window positions, sizes, dock widths, ordering and minimised state all survive. The only thing removed is the stuck 300px height that causes the bug, and only where it exactly matches the old default.
Two things worth knowing:
Version 4 is the only version anyone actually has. The counter was introduced at 4 and has never been bumped since, so there are no older layouts out in the wild to discard.
The bump is what keeps this a one-time cleanup. We cannot tell the old stamped 300 apart from someone who deliberately dragged a panel to exactly 300, so there is a judgement call either way. With the version bump it happens once: after a user next moves a window their layout is marked as migrated, and from then on a deliberate 300 sticks. Without the bump we would have to strip 300 on every single load, forever, which would permanently stop anyone from choosing that height on purpose.
On that judgement call — landing on exactly 300 by hand is very unlikely anyway. Resizing starts from the measured content height, so drags land on fractional values, and the minimum heights in play are 50 and 280, so nothing snaps to 300.
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.
^ ai comment
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.
But it is valid; when I tested locally it did not reset my window layout. The only windows that will be reset are ones that are exactly 300px high