Expanding to Chromium.

[c4lliope]

I am debugging the extension in both Brave and Chromium.

As you say, this seems to display no problems in Firefox.

In these two chromium-based browsers, I see an error like so:

The implication is that background-script.js is failing to run.

I am now learning a bunch about extension background scripts. Oh no. Link dump:

• https://stackoverflow.com/questions/9106519
• https://stackoverflow.com/questions/44673632
• https://discourse.mozilla.org/t/error-could-not-establish-connection-receiving-end-does-not-exist/32355
• https://developer.chrome.com/docs/extensions/get-started/tutorial/scripts-on-every-tab
• https://developer.chrome.com/docs/extensions/develop/concepts/content-scripts
• https://medium.com/better-programming/how-to-write-a-background-script-for-chrome-extension-ad76875eb6cd

[c4lliope]

Whereas Mozilla likes to see:

    "background": {
        "scripts": [
            "js/browser-polyfill.js",
            "js/background-script.js"
        ],
    },

I could only get the background script recognized in Chromium browsers using:

    "background": {
        "service_worker": "js/background-script.js"
    },

or:

    "background": {
        "service_worker": "js/background-script.js",
        "type": "module"
    },

Both of these seem to be a problem because the browser polyfill is missing.
I'm unsure, but this is probably the reason that service worker displays as inactive.

I'm considering bumping back to manifest v2, if the background.scripts key is recognized by that version.

[fmartingr]

My main browser is Comet, which is chromium based, and the extension works perfectly. I'm using the build from #89 since that's what I'm working on right now. Can you try that one? I'm not sure why it doesn't work in other browsers.

You have make build and make build-chromium, are you using the latter?