Skip to content

Fix #38690: Explain persistence of registered content scripts across browsers #38746

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mastaan66 wants to merge 5 commits into from
Closed

Fix #38690: Explain persistence of registered content scripts across browsers #38746

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
05b2f8a
Update index.md
mastaan66 Mar 21, 2025
d9d3b92
Update index.md
mastaan66 Mar 21, 2025
c80db90
Update index.md
mastaan66 Mar 21, 2025
079452c
Editorial fixes
Josh-Cena Mar 21, 2025
64b4f9f
Merge branch 'main' into patch-2
mastaan66 Mar 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion ...-us/mozilla/add-ons/webextensions/api/scripting/registercontentscripts/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,14 @@ await browser.scripting.registerContentScripts(

### Return value

A [`Promise`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) fulfilled with no arguments or rejected when there are errors. Errors can occur during script parsing and file validation or if the IDs specified exist. When an error occurs, no scripts are registered.
A [`Promise`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) is fulfilled with no arguments or rejected when there are errors. Errors can occur during script parsing and file validation or if the IDs specified exist. When an error occurs, no scripts are registered.

> [!NOTE]
> Persistence of registered scripts:
>
> - In Firefox, registered scripts are removed when the extension is unloaded or reloaded.
> - In Chrome, registered scripts persist across restarts if `persistAcrossSessions: true`, but they are unregistered when the extension is updated.
> - The `persistAcrossSessions` property controls whether scripts remain registered across browser sessions.

## Examples

Expand Down