InjectionResult.error is not supported by Chrome (mdn#25624)

* InjectionResult.error is not supported by Chrome Clarify `scripting.executeScript()` (WebExtensions) error handling in Chrome that differs from Firefox. * Reference a Chromium issue for scripting.InjectionResult.error Co-authored-by: Rob Wu <[email protected]> --------- Co-authored-by: Rob Wu <[email protected]>
MarkLodato · Mar 29, 2023 · 33a8d9c · 33a8d9c
1 parent 5be5b68
commit 33a8d9c
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/files/en-us/mozilla/add-ons/webextensions/api/scripting/executescript/index.md b/files/en-us/mozilla/add-ons/webextensions/api/scripting/executescript/index.md
@@ -61,6 +61,8 @@ Each `InjectionResult` object has these properties:
 - `error` {{optional_inline}}
   - : `any`. If an error occurs, contains the value the script threw or rejected with. Typically this is an error object with a message property but it could be any value (including primitives and undefined).
 
+    Chrome does not support the `error` property yet (see [Issue 1271527: Propagate errors from scripting.executeScript to InjectionResult](https://crbug.com/1271527)). As an alternative, runtime errors can be caught by wrapping the code to execute in a try-catch statement. Uncaught errors are also reported to the console of the target tab.
+
 The result of the script is the last evaluated statement, which is similar to the results seen if you executed the script in the [Web Console](https://firefox-source-docs.mozilla.org/devtools-user/web_console/index.html) (not any `console.log()` output). For example, consider a script like this:
 
 ```js