-
Mozilla have announced plans to phase out all non-WebExtension add-ons by the end of 2017. While I consider this decision to be utterly insane (and half expect them to end up extending that deadline, …
-
Most Chrome extensions work with no modifications in Firefox
https://vimeo.com/241435808
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs
-
MDN URL: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions
#### What information was incorrect, unhelpful, or incomplete?
Related issues: https://github.com/mdn/browser-comp…
-
## Background
> WebExtensions are a cross-browser system for developing browser add-ons.
Firefox has a transparent process for [triaging](https://wiki.mozilla.org/WebExtensions/Triage) requests …
lidel updated
5 years ago
-
We are currently in the middle of trying to move non-web platform docs off MDN, and this issue serves as a record of what is needed for webextensions. We have the add-ons landing page — https://develo…
-
As I'm sure you know, in November 2017, the Firefox 57 release will disable all addon APIs with the exception of the new WebExtensions API. Are there any plans for undertaking this transition, or aud…
-
We now have https://github.com/electron/electron/issues/5842 for Accessibility DevTools extension.
How about implementing more WebExtensions APIs to support more extensions that are on chrome and FF.
-
Mozilla will be [dropping support](https://blog.mozilla.org/addons/2017/02/16/the-road-to-firefox-57-compatibility-milestones/) for XUL extensions in Firefox 57, so this needs to be ported to the WebE…
-
This is a problem with current WebExtensions APIs: we can either guarantee injection (into a frame) before anything else will happen, or we can inject conditionally/pass configuration to the injected …
-
Several of the examples here pull in dependencies for stuff like react, babel, webpack, eslint. They are useful to show how WebExtensions can integrate these technologies, but I think they are outside…