Repository navigation
Chore: Pin the window modules at the fork's multi-window merge (FR-53) - #369
Merged
Merged
Conversation
… shared display connection
This was referenced Oct 29, 2026
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.
Refs #355. Moves WINDOW_REVISION only, from 2eb80c1 to 317d380 (fork #176, several windows per process, and #173). Nothing in the renderer uses the new window members yet, so this proves the fork's window rewrite (shared X11 connection, per-window Win32 state, AppKit delegates) does not change the single-window renderers. The Linux layout test reads the event loop in the shared X11 connection now. Proof: heavy CI (run-heavy-ci).