How to use this in Firefox?

[chrisbacke]

I see the manifest.firefox.json file but... have no idea how to use it? Any chance of adding it to the official Firefox add-on store, or giving some directions for going from Github to Firefox?

Thanks so much =)

[Terrance]

The Firefox manifest is there somewhat experimentally -- at the time of adding it, Firefox's support for WebExtensions was limited (notably not supporting optional site permissions, service workers or private browsing access) and wouldn't load the Chrome manifest as-is. Whilst I switched to Firefox as my daily driver a while back, I don't use Homely as the built-in new tab page has been sufficient for me.

That said, if you want to give it a spin, the steps to install it in Firefox should be something like:

1. Clone or download a static copy of the repo
2. Replace manifest.json with a copy of manifest.firefox.json (by default it links to manifest.chrome.json)
3. Open about:addons in Firefox
4. To load unpacked (doesn't persist between sessions):
   a. In Firefox: ⚙ > Debug Add-ons, then Load Temporary Add-on...
   b. Browse to and select the manifest.json file
5. To load packed:
   a. Create a ZIP folder of manifest.json, lib and res
   b. Rename it so the file extension is .xpi
   c. In Firefox: ⚙ > Install Add-on From File...
   d. Browse to and select the renamed ZIP folder

[chrisbacke]

Alright, so it worked unpacked, but when I tried to pack it according to these instructions, Firefox says it's corrupt.

[Terrance]

Apparently so, with no additional information...

After a few stabs in the dark, I've found that Manifest v3 extensions now require an ID in the manifest, so adding one (note that it has to be in the form of a UUID inside braces) seems to get past that initial validation:

{
    "browser_specific_settings": {
        "gecko": {
            "id": "{14fb1250-54e8-11ef-bd44-00155db34f4c}"
        }
    },
    "name": "Homely",
    ...
}

At this point Firefox now blocks the installation because it isn't signed, so presumably I would need to submit it to the Mozilla add-on site for signing, which itself will probably require going through and seeing what still doesn't work -- I don't think Firefox support here will be in a state where it's ready to use.

You can alternatively disable signature verification, though end-users should probably not be doing that without good reason.

[chrisbacke]

As always, your hard work is greatly appreciated!

I'm one of those that's finally switching from Chrome to Firefox with all the Manifest v3 changes, and this is one of two extensions that is making it hard to completely switch over.