CODEWITHSUNDEEP
google-chrome-extension
Gil Goldshlager
Gil Goldshlager

Reputation: 771

Background script only for specific domain in Chrome extension

I would like to know how to run the background script of a Chrome extension for only specific/specified domain/s please?

For example, if an extension is meant to run only on pages of Google.com, so there is no reason to keep the background script running on any other domains.

In my manifest file I have set "matches" but I can still see the background script running on every domain and tab.

...

"background": {
    "matches": [
        "*://*.google.com/*"
    ],
    "scripts": ["scripts/background.js"],
    "persistent": false
},

"content_scripts": [
    {
        "matches": [
            "*://*.google.com/*"
        ],
        "css": ["styles/default.css"],
        "js": ["scripts/jquery.js", "scripts/default.js"]
    }
],

"permissions": [
    "storage",
    "declarativeContent",
    "tabs"
],

...

Edit
To add more info that will help understand my goal:
I have a content script and a popup, the popup is being used as a remote control with options to choose from and play with, that will eventually effects the page.
When changing an option in the popup, it sends it's value to the background/event script, there it being temporary saved in a variable, and then being sent to the content script, where it actually being executing and show up on the page to the user.
And I want that only when the user leaves the specific domain, the background/event script will save the settings to storage, so by that there will be only a single storage saving task and NOT each time the user is changing a setting in the popup.
After the settings got saved to storage and the user left, I want nothing to run it the background anymore please.

Upvotes: 4

Views: 8794

Answers (1)

Xan
Xan

Reputation: 77541

You are misunderstanding what the background page is for, and what "persistent": false means.

The background page does not run "for" any domain; it just runs. A single copy per extension. Have a look at the Architecture Overview.

However, if you are concerned that it consumes resources, you add "persistent": false to the manifest. This makes it an Event page, that is unloaded when it's not doing work.

If your event page is woken up only by content scripts, then you have achieved your goal: it won't be running when it's not needed.

It's entirely up to you to properly construct the background page so it's idle when you don't need it. Since you haven't told what it's supposed to be doing - well..

Do read the Event page documentation, there are important restrictions you need to understand.

Upvotes: 3

Related Questions