Skip to content
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.

Sign up for GitHub

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

Jump to bottom

docs: errors in isolated world are not dispatched #24016

Merged
merged 3 commits into from Jun 8, 2020
Merged

docs: errors in isolated world are not dispatched #24016

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ed38ba9
docs: errors in isolated world are not dispatched
zcbenz Jun 8, 2020
a89476a
empty commit
ckerr Jun 8, 2020
7f1efe9
fix manual oops
ckerr Jun 8, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/api/web-frame.md
View file
Open in desktop
Expand Up @@ -154,10 +154,14 @@ this limitation.
* `userGesture` Boolean (optional) - Default is `false`.

Returns `Promise<any>` - A promise that resolves with the result of the executed code
or is rejected if the result of the code is a rejected promise.
or is rejected if execution could not start.

Works like `executeJavaScript` but evaluates `scripts` in an isolated context.

Note that when the execution of script fails, the returned promise will not
reject and the `result` would be `undefined`. This is because Chromium does not
dispatch errors of isolated worlds to foreign worlds.

### `webFrame.setIsolatedWorldInfo(worldId, info)`
* `worldId` Integer - The ID of the world to run the javascript in, `0` is the default world, `999` is the world used by Electrons `contextIsolation` feature. Chrome extensions reserve the range of IDs in `[1 << 20, 1 << 29)`. You can provide any integer here.
* `info` Object
Expand Down