feat: add preload-error event to webContents
#16411
Merged
Conversation
This file contains 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
miniak
force-pushed
the
miniak/preload-error
branch
from
5ecbf8b
to
1e6454d
Compare
alexeykuzmin
approved these changes
Jan 15, 2019
ppontes
approved these changes
Jan 16, 2019
codebytere
approved these changes
Jan 17, 2019
|
Release Notes Persisted
|
akisctx
pushed a commit
to akisctx/electron
that referenced
this pull request
Jan 22, 2019
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.
Description of Change
Currently there is no good way of telling if the preload script failed (such as unhandled exception)
/cc @nornagon, @MarshallOfSound
Checklist
npm testpassesRelease Notes
Notes: Added
preload-errorevent towebContentsemitted when preload script fails (parse error, unhandled exception, etc.)