fix: constrain browser window to VNC framebuffer#47
Open
shellus wants to merge 1 commit into
Open
Conversation
|
To great |
Martin-Hausleitner
added a commit
to Martin-Hausleitner/CloakBrowser-Manager
that referenced
this pull request
Jul 24, 2026
feat: integrate PR CloakHQ#47, PR CloakHQ#27, PR CloakHQ#26, profile health & read-only extension inventory
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
2 participants
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.
Summary\n- resize and reposition the native browser window when it overflows the VNC framebuffer\n- use the profile screen size as the framebuffer boundary\n- add a regression test for oversized/offscreen window bounds\n\n## Tests\n- pytest backend/tests/test_browser_manager.py -k fit_window_to_vnc\n\n## Notes\n- This PR intentionally excludes local Dockerfile mirror changes from my deployment environment.