Firefox add-on for Hatch

Bug #1731922 reported by Galen Charlton on 2017-11-13
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Wishlist
Unassigned

Bug Description

It would be nice to have a Firefox add-on for Hatch, similar to the Chrome extension, that is available from the FF add-on store.

Tasks include:

- writing the extension (which hopefully will mostly be a matter of porting the Chrome extension)
- setting up a developer account (see https://addons.mozilla.org/en-US/developers/)
- creating FF versions of the logo and images if the ones devised for the Chrome extension won't do

Terran McCanna (tmccanna) wrote :

+1

Chris Sharp (chrissharp123) wrote :

I've done some work on this today, available at http://git.evergreen-ils.org/?p=working/Hatch.git;a=shortlog;h=refs/heads/user/csharp/lp1731922_firefox_hatch. Hoping to get some other eyes on this and make some progress towards a publishable add-on for the Firefox site.

Changed in evergreen:
status: New → Confirmed
Jason Boyer (jboyer) wrote :

I have done battle with Firefox Native Messaging support and have finally found myself on the other side. Here is a branch that modifies the batch file, installer, and adds a new manifest for the NativeMessagingHosts entry. The latter is necessary because FF flames out if you try to mix Chrome and FF support in a single manifest while Chrome just Does The Thing. :-/

http://git.evergreen-ils.org/?p=working/Hatch.git;a=shortlog;h=refs/heads/user/jboyer/lp1731922_ff_support

Note it also makes some minor changes to the extension code, so the FF extension currently in place will need to be updated. The Chrome version isn't as urgent but should also be kept in sync. Chrome gives a warning when loading an extension manifest with the (required by FF) applications key, so if that's a showstopper on the Chrome side then we'll ALSO need to have separate extension manifests. :(

Finally, Firefox has no way to auto-install a regular extension from the addon site through the Windows registry the way Chrome does. (If you install an extension through the registry it has to be locally installed and can't be auto-updated). For that reason we should probably include links to both extensions on the Hatch workstation admin page so users can find them with a minimum of hassle. But that's for another LP...

Jason Boyer (jboyer) on 2018-05-18
tags: added: pullrequest
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers