2 ms·
We will also continue supporting SDK add-ons as long as they don’t use require(‘chrome’) or some of the low-level APIs that provide access to XUL elements. See
by sp332 11y ago
We will also continue supporting SDK add-ons as long as they don’t use require(‘chrome’) or some of the low-level APIs that provide access to XUL elements.
Seems like there's still a lot of power available, if you really want to dive in.
- the8472 11y ago> as long as they don’t use require(‘chrome’) or some of the low-level APIs That's the powerful parts. The high-level APIs are fairly restrictive, quite similar to chrome APIs, maybe even less powerful on their own.
- sp332 11y agoI don't know if that means that they will be disallowed, or just maybe broken.
- the8472 11y agoMozilla has an add-on review process in place. So you probably wouldn't get a new addon approved that relies on those APIs. And with enforced signature signing you can't even distribute it to users yourself. So effectively it will restrict extension-development to a whitelist of APIs. Everything else will be verboten, maybe with varying degrees of enforcement. It certainly doesn't sounds like an open system to me.
- Ar-Curunir 11y agoWhat'll happen to amazing addons like pentadactyl and vimperator? These are vastly more useful than their Chrome/Chromium counterparts.
- wldcordeiro 11y agoThey're completely broken. Vimperator has an issue on github about getting e10s support but it looks like with these changes it doesn't matter Firefox will permanently break or cripple them.
- Tobu 11y agoThey'll probably be less broken, with a proper API: https://wiki.mozilla.org/WebExtensions#Additional_APIs https://wiki.mozilla.org/WebExtensions#Additional_APIs That kind of keyboard permission could be used for keyloggers though, it's not something every extension should get.