-
Notifications
You must be signed in to change notification settings - Fork 15.8k
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
fix: remove non-existent gpu-crashed event on <webview> #17317
Conversation
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.
Lol... Where did this go, oh well
Release Notes Persisted
|
@miniak , can you please backport it to |
/trop run backport-to 4-1-x |
The backport process for this PR has been manually initiated, |
/trop run backport-to 5-0-x |
The backport process for this PR has been manually initiated, |
I was unable to backport this PR to "4-1-x" cleanly; |
I was unable to backport this PR to "5-0-x" cleanly; |
A maintainer has manually backported this PR to "4-1-x", please check out #18003 |
1 similar comment
A maintainer has manually backported this PR to "4-1-x", please check out #18003 |
A maintainer has manually backported this PR to "5-0-x", please check out #18004 |
1 similar comment
A maintainer has manually backported this PR to "5-0-x", please check out #18004 |
@alexeykuzmin backported, those branches are affected too |
Description of Change
There is no such event implemented.
WebContents
would have to emitgpu-crashed
(similar tocrashed
andplugin-crashed
).Checklist
npm test
passesRelease Notes
Notes: Remove non-existent
gpu-crashed
event on<webview>
.