Bug 1930776 updates for the implementation of userScripts.execute

[rebloor]

Description

Documents the implementation of userScripts.execute() in Firefox 153 (bug 1930776).

• Adds a Firefox 153 release note for userScripts.execute().
• Updates the userScripts API overview page to include execute() in the "Execution worlds" section and in the ExecutionWorld type description, both of which previously only referenced register() and update().

Related issues and pull requests

BCD changes in mdn/browser-compat-data#29811

[github-actions]

Preview URLs (3 pages)

• /en-US/docs/Mozilla/Add-ons/WebExtensions/API/userScripts/ScriptSource
• /en-US/docs/Mozilla/Add-ons/WebExtensions/API/userScripts
• /en-US/docs/Mozilla/Firefox/Releases/153

Flaws (1)

Note! 2 documents with no flaws that don't need to be listed. 🎉

Found an unexpected or unresolvable flaw? Please report it here.

URL: /en-US/docs/Mozilla/Add-ons/WebExtensions/API/userScripts
Title: userScripts
Flaw count: 1

• unknown:
  • must be provided

External URLs (2)

URL: /en-US/docs/Mozilla/Firefox/Releases/153
Title: Firefox 153 release notes for developers (Nightly)

• https://bugzil.la/1930776 (1 time) (Note! This may be a new URL 👀)
• https://bugzil.la/2044712 (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2026-06-10 16:55:39)

[Rob--W]

Please update the description of ScriptSource to also reference userScripts.execute in the intro at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/userScripts/ScriptSource

[Rob--W]

Reduced ambiguity.

Suggested change

	When a user script is registered, updated, or executed (using {{WebExtAPIRef("userScripts.register()")}}, {{WebExtAPIRef("userScripts.update()")}}, or {{WebExtAPIRef("userScripts.execute()")}}), your extension can set it to run in an isolated `USER_SCRIPT` world or the `MAIN` world.
	When a user script is registered or updated (using {{WebExtAPIRef("userScripts.register()")}} or {{WebExtAPIRef("userScripts.update()")}}) or executed (using {{WebExtAPIRef("userScripts.execute()")}}), your extension can set it to run in an isolated `USER_SCRIPT` world or the `MAIN` world.

[rebloor]

@Rob--W as rewritte, this now says that userScripts.register can register or update, and userScripts.update can register or update. Unless there's something missing from the documentation, I don't think that's the case.
However, I think this might address your concern.

Suggested change

	When a user script is registered, updated, or executed (using {{WebExtAPIRef("userScripts.register()")}}, {{WebExtAPIRef("userScripts.update()")}}, or {{WebExtAPIRef("userScripts.execute()")}}), your extension can set it to run in an isolated `USER_SCRIPT` world or the `MAIN` world.
	When a user script is registered, updated, or executed (using {{WebExtAPIRef("userScripts.register()")}}, {{WebExtAPIRef("userScripts.update()")}}, and {{WebExtAPIRef("userScripts.execute()")}} respectively), your extension can set it to run in an isolated `USER_SCRIPT` world or the `MAIN` world.

[Rob--W]

Is this "Other" header something new? We haven't used that before. I double checked the last 10 releases and we only used a list of bullet points.

Suggested change

### Other

[rebloor]

At least recently, it's always been in the template, but I usually put the additions immediately below the section title.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.