-
Notifications
You must be signed in to change notification settings - Fork 67
Skip chromium restart on headful display resize #262
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
+759
−37
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
0e5d161
Skip chromium restart on headful display resize
hiroTamada 49dfe3f
Drop legacy chromium-restart branch on Xorg path
hiroTamada 5b968a6
Drop redundant headful subtests that flake under CI container churn
hiroTamada 9f62371
Fix xrandr output, fail closed on CDP, assert windowID/state stable
hiroTamada b336687
Always use --mode in xrandr resize; --size is incompatible with --output
hiroTamada 42caab4
Make resize synchronous + add non-Neko Xorg coverage
hiroTamada ea9dd74
Extract firstPageTargetID helper to deduplicate CDP boilerplate
hiroTamada 2f81c56
Address PR review: X-root poll, simpler CDP path, doc fixes
hiroTamada 0bad77e
Fix outdated comment claim about Neko + xrandr asterisk
hiroTamada 7f4d47d
waitForXRootSize: call getCurrentResolutionFromXrandr directly
hiroTamada 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.
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.
X root poll uses unreliable
grep '*'after Neko resizeMedium Severity
waitForXRootSizecallss.getCurrentResolution(), which internally runsxrandr | grep -E '\\*'to find the active mode. However, the new test helpergetXRootResolutionin the same PR explicitly avoids the*-grep approach, with a comment explaining that "Xorg-with-Neko surfaces a synthetic active mode that xrandr does not mark with an asterisk." If this is accurate,waitForXRootSizewill always time out on the Neko path after a resize because the new mode won't have a*marker, causingPATCH /displayto return a 500 even though the resize succeeded.Additional Locations (1)
server/e2e/e2e_display_resize_window_test.go#L75-L112Reviewed by Cursor Bugbot for commit 2f81c56. Configure here.
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.
checking on this. I did not see this issue when I was testing
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.
Right — the bot was working off a wrong claim in my test-helper doc, not a real bug. Verified in a running container on this branch + Neko enabled:
Neko's active mode IS marked with
*after a resize, so the server'sgetCurrentResolutionFromXrandrworks fine. The benchmark above (~76ms median over 8 iterations) is the empirical confirmation that the polling loop converges quickly.Fixed the stale doc claim in 0bad77e — no server code change needed.
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.
Good catch — fixed in 7f4d47d. Now calls
getCurrentResolutionFromXrandrdirectly, so the post-condition is bound to the X root regardless of whether anyone ever sets a viewportOverride on the Xorg path. Doc comment updated to call out why the higher-level wrapper is the wrong abstraction here.