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
feat: add new render-process-gone event #23096
Conversation
bc9bb65
to
b32549e
Compare
Release Notes Persisted
|
/trop run backport-to 8-x-y |
The backport process for this PR has been manually initiated - |
I have automatically backported this PR to "8-x-y", please check out #24308 |
/trop run backport-to 9-x-y |
The backport process for this PR has been manually initiated - |
I have automatically backported this PR to "9-x-y", please check out #24309 |
@MarshallOfSound Can I safely access the |
Maybe this PR addresses that concern |
electron/electron#23096 License: MIT Signed-off-by: Henrique Dias <hacdias@gmail.com>
electron/electron#23096 License: MIT Signed-off-by: Henrique Dias <hacdias@gmail.com>
electron/electron#23096 License: MIT Signed-off-by: Henrique Dias <hacdias@gmail.com>
* refactor: replace deprecated 'crashed' event electron/electron#23096 * feat: ux element when window becomes unresponsive * style: improved helptext dedicated button labels remove any ambiguity Co-authored-by: Marcin Rataj <lidel@lidel.org>
The
crashed
event could fire for a number of reasons, some of which are nothing to do with crashes. It also was losing some helpful information about why the process crashed. This PR leaves that event untouched (as per our new breaking changes policy) and adds a new event that contains more information (the actualreason
the process crashed) and puts it in an object for easier expandability later.Notes: Added new
render-process-gone
event to replace thecrashed
event.