From bb452b468b90cb672a8144f2c6617949c9564dcf Mon Sep 17 00:00:00 2001 From: Cheng Zhao Date: Mon, 8 Jun 2020 12:42:44 -0500 Subject: [PATCH] docs: errors in isolated world are not dispatched --- docs/api/web-frame.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/api/web-frame.md b/docs/api/web-frame.md index e88fecbf3fd31..e26efe6b7cab7 100644 --- a/docs/api/web-frame.md +++ b/docs/api/web-frame.md @@ -141,10 +141,14 @@ this limitation. * `userGesture` Boolean (optional) - Default is `false`. Returns `Promise` - 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 +and the `result` would be `undefined`. This is because Chromium does not +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