fix: setIgnoreMouseEvents forward subclass invalidates after web content view change - #52633
Draft
YUCLing wants to merge 1 commit into
Draft
fix: setIgnoreMouseEvents forward subclass invalidates after web content view change#52633YUCLing wants to merge 1 commit into
YUCLing wants to merge 1 commit into
Conversation
YUCLing
changed the title
YUCLing
force-pushed
the
fix/set-ignore-mouse-events-crash-issue
branch
2 times, most recently
from
August 4, 2026 17:49
393933e to
b954c6d
Compare
YUCLing
changed the title
YUCLing
force-pushed
the
fix/set-ignore-mouse-events-crash-issue
branch
2 times, most recently
from
August 5, 2026 16:32
debe059 to
7e86d17
Compare
6 tasks
YUCLing
changed the title
7 tasks
YUCLing
force-pushed
the
fix/set-ignore-mouse-events-crash-issue
branch
from
August 6, 2026 05:03
7e86d17 to
2e51ab6
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
1 participant
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.
Description of Change
Fixes #49982
Fixes #48035
Fixes #30808 (partially, #52631 will fix the other part of it)
Also fixed the same glitch caused by simple refreshes.
The original approach that was used to fetch the legacy window will never be updated after the actual legacy window has been updated. Now a on-demand fetching and polling check approach is used to solve the issue.
Before
After
Checklist
npm testpassesRelease Notes
Notes: Fixed
setIgnoreMouseEventswill be stuck inside a forever click-through/glitched state after renderer crash.