summaryrefslogtreecommitdiffstats
path: root/toolkit/components/extensions/docs
diff options
context:
space:
mode:
Diffstat (limited to 'toolkit/components/extensions/docs')
-rw-r--r--toolkit/components/extensions/docs/webext-storage.rst2
-rw-r--r--toolkit/components/extensions/docs/webidl_bindings.rst2
2 files changed, 2 insertions, 2 deletions
diff --git a/toolkit/components/extensions/docs/webext-storage.rst b/toolkit/components/extensions/docs/webext-storage.rst
index 9b5f2428d6..27ba3ad4d7 100644
--- a/toolkit/components/extensions/docs/webext-storage.rst
+++ b/toolkit/components/extensions/docs/webext-storage.rst
@@ -207,7 +207,7 @@ the actual result of the function (also a set of changes to send to observers, b
beyond this doc).
Ultimately, the `PuntResult` ends up back on the main thread once the call is complete
-and arranges to callback the JS implementation, which in turn resolves the promise created in `ExtensionStorageSync.jsm`
+and arranges to callback the JS implementation, which in turn resolves the promise created in `ExtensionStorageSync.sys.mjs`
End result:
-----------
diff --git a/toolkit/components/extensions/docs/webidl_bindings.rst b/toolkit/components/extensions/docs/webidl_bindings.rst
index be8c63d0a7..7f7f2e53cb 100644
--- a/toolkit/components/extensions/docs/webidl_bindings.rst
+++ b/toolkit/components/extensions/docs/webidl_bindings.rst
@@ -4,7 +4,7 @@ WebIDL WebExtensions API Bindings
While on ``manifest_version: 2`` all the extension globals (extension pages and content scripts)
that lives on the main thread and the WebExtensions API bindings can be injected into the extension
global from the JS privileged code part of the WebExtensions internals (`See Schemas.inject defined in
-Schemas.jsm <https://searchfox.org/mozilla-central/search?q=symbol:Schemas%23inject&redirect=false>`_),
+Schemas.sys.mjs <https://searchfox.org/mozilla-central/search?q=symbol:Schemas%23inject&redirect=false>`_),
in ``manifest_version: 3`` the extension will be able to declare a background service worker
instead of a background page, and the existing WebExtensions API bindings can't be injected into this
new extension global, because it lives off of the main thread.