Convert to a WebExtension

[ExE-Boss]

In Firefox 57, Mozilla will be dropping legacy add-ons (SDK, XUL and XPCOM), and replacing them with the WebExtensions API.
This API is partially based off of Chrome’s extension API and is multi-process by design.

MDN resources

https://developer.mozilla.org/en-US/Add-ons/WebExtensions
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Porting_a_Google_Chrome_extension
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Porting_a_legacy_Firefox_add-on

Additional resources

https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/
https://blog.mozilla.org/addons/2016/09/13/webextensions-and-parity-with-chrome/
https://wiki.mozilla.org/Add-ons/2017

[MartinNowak]

This is necessary to support the new multi-process feature that was now enabled by default in the just released Firefox 54.

[MartinNowak]

Should (hopefully) not be too much effort to make the chrome WebExtension work on Firefox.

[ExE-Boss]

I have already tested it with Chrome Store Foxified and it mostly worked. The main issue is that the custom CSS that is injected to add code coverage information is for some reason different between the SDK extension and the Chrome extension.

[keimlink]

@stevepeak Do you have a roadmap to upgrade the Firefox extension?

[stevepeak]

Hey! We are hiring a consultant to upgrade the extension within the month. Hope to have it complete within 4 weeks.

[tmc]

@stevepeak any update here? maybe just adding some direction for an OSS contributor if the contractor plan has fallen through?

[stevepeak]

Starting this next week! If anyone would like to help out please let us know. 👍

[JelteF]

@ExE-Boss thanks for the suggestion of Chrome Store Foxified. For me it seems to work fine at the moment.

@stevepeak any updates on this?

[cadesalaberry]

@stevepeak I would love to get some updates on the status of the development. Has some development started already?