contentScripts.register()
Use this function to register one or more content scripts.
It accepts one parameter, which is an object with similar properties to the objects given in the content_scripts
manifest key (but note that content_scripts
is an array of objects, while the argument to register()
is a single object).
This is an asynchronous function that returns a Promise
.
Syntax
let registering = browser.contentScripts.register(
contentScriptOptions // object
)
Parameters
contentScriptOptions
-
object
. ARegisteredContentScriptOptions
object representing the content scripts to register. It has similar syntax to the objects in thecontent_scripts
manifest key array. The differences are:- property names use camelCase, rather than underscores (for example,
excludeMatches
, notexclude_matches
- the
js
andcss
properties allow you to register strings as well as URLs, so their syntax has to distinguish these types.
The
RegisteredContentScriptOptions
object has the following properties:allFrames
Optional-
Same as
all_frames
in thecontent_scripts
key. -
A string or array of strings. Registers the content script in the tabs that belong to one or more cookie store IDs. This enables scripts to be registered for all default or non-contextual identity tabs, private browsing tabs (if extensions are enabled in private browsing), the tabs of a contextual identity, or a combination of these.
css
Optional-
An array of objects. Each object has either a property named
file
, which is a URL starting at the extension's manifest.json and pointing to a CSS file to register, or a property namedcode
, which is some CSS code to register. excludeGlobs
Optional-
Same as
exclude_globs
in thecontent_scripts
key. excludeMatches
Optional-
Same as
exclude_matches
in thecontent_scripts
key. includeGlobs
Optional-
Same as
include_globs
in thecontent_scripts
key. js
Optional-
An array of objects. Each object has either a property named
file
, which is a URL starting at the extension's manifest.json and pointing to a JavaScript file to register, or a property namedcode
, which is some JavaScript code to register. matchAboutBlank
Optional-
Same as
match_about_blank
in thecontent_scripts
key. matches
-
Same as
matches
in thecontent_scripts
key. runAt
Optional-
Same as
run_at
in thecontent_scripts
key.
- property names use camelCase, rather than underscores (for example,
Return value
A Promise
that will be fulfilled with a contentScripts.RegisteredContentScript
object that you can use to unregister the content scripts.
Currently, content scripts are unregistered when the related extension page (from which the content scripts were registered) is unloaded, so you should register a content script from an extension page that persists at least as long as you want the content scripts to stay registered.
Browser compatibility
BCD tables only load in the browser
Examples
This example registers the defaultCode
content script for all .org
URLs:
const defaultHosts = "*://*.org/*";
const defaultCode = "document.body.innerHTML = '<h1>This page has been eaten<h1>'";
async function register(hosts, code) {
return await browser.contentScripts.register({
matches: [hosts],
js: [{code}],
runAt: "document_idle"
});
}
let registered = register(defaultHosts, defaultCode);
This code registers the JS file at content_scripts/example.js:
const scriptObj = await browser.contentScripts.register({
"js": [{file: "/content_scripts/example.js"}],
"matches": ["<all_urls>"],
"allFrames": true,
"runAt": "document_start"
});