Pchen0/electron

docs: errors in isolated world are not dispatched (#24016)

* docs: errors in isolated world are not dispatched

* empty commit

* fix manual oops

Co-authored-by: Cheng Zhao <[email protected]>

Charles Kerr 4 years ago

parent

a06170648c

commit

547e50c699

1 changed files with 5 additions and 1 deletions

Split View Show Diff Stats

						
							+ 5
							
							- 1
						
docs/api/web-frame.md
							 
								View File
							
				@@ -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

docs: errors in isolated world are not dispatched (#24016)

+ 5 - 1 docs/api/web-frame.md View File

+ 5 - 1
docs/api/web-frame.md
View File