Repository navigation
Conversation
rafaumeu
force-pushed
the
fix/window-bounds-workarea
branch
from
October 26, 2026 13:49
2b0a2cc to
438ac62
Compare
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.
Fixes #1057.
Saved window dimensions can exceed the current monitor work area after a display configuration change, or be invalid.
Restore the saved size within the window monitor work area, with a valid lower bound, falling back to the saved dimensions when monitor detection is unavailable.
Tested with
python3 -m py_compile usr/lib/linuxmint/mintUpdate/mintUpdate.py,git diff --check, and a local GTK/Gdk work-area bounds harness../testwas not run because it modifies/usr.AI-assisted research and draft; independently reviewed and tested locally.