Extension compatibility with Basilisk Topic is solved

Board for discussions around the Basilisk web browser.

Moderator: satrow

User avatar
Gauri
New to the forum
New to the forum
Posts: 2
Joined: Thu, 08 Nov 2018, 09:25

Extension compatibility with Basilisk

Unread postby Gauri » Thu, 08 Nov 2018, 10:01

Some extensions fail to install with an error "This add-on could not be installed because it appears to be corrupt" although "Load Temporary Add-on" at about:debugging works fine for them. As an example I can give this small extention: https://addons.mozilla.org/en-US/firefo ... -playback/
What should I change in .xpi to make it compatible with Basilisk?

yami_
Fanatic
Fanatic
Posts: 209
Joined: Thu, 26 Apr 2018, 11:05

Re: Extension compatibility with Basilisk  Topic is solved

Unread postby yami_ » Thu, 08 Nov 2018, 11:43

Basilisk only supports web extensions in gecko-targe mode. Since this extension does not specifically targets Gecko it appears to be corrupt from the browser point of view. You would probably need to add the "applications": { "gecko": { /* ... */} } section with an id and maybe strict_min_version attributes in the manifest. See here for more information about those attributes.
cat came back from Berkeley waving flags
- rob pike

User avatar
Gauri
New to the forum
New to the forum
Posts: 2
Joined: Thu, 08 Nov 2018, 09:25

Re: Extension compatibility with Basilisk

Unread postby Gauri » Mon, 12 Nov 2018, 11:24

yami_ wrote:You would probably need to add the "applications"

Thanks a lot! It works! strict_min_version is not needed, just

Code: Select all

  "applications": {
    "gecko": {
      "id": "{3371817b-c227-4ba0-b5da-6c9d111e994d}"
    }
  },
was enough.

Now a bit more sofisticated case: https://addons.mozilla.org/en-US/firefox/addon/browsec
I added

Code: Select all

  "applications": {
    "gecko": {
      "id": "browsec@browsec.com"
    }
  }
and removed strict_min_version. As a result, the extension is successfully installed, but clicking on its button results in an empty popup page. I guess that the error is in popup/popup.html but can't find out where exactly it is. Could you help me?


Return to “Basilisk”

Who is online

Users browsing this forum: JoeyG and 2 guests