News for hackers. Stuff that matters.
Re:The Future of Developing Firefox Add-ons by sp332 on Friday August 21, 2015 @11:10AM (#10097991)
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.

Re:The Future of Developing Firefox Add-ons by Ar-Curunir on Friday August 21, 2015 @11:34AM (#10098164)
What'll happen to amazing addons like pentadactyl and vimperator? These are vastly more useful than their Chrome/Chromium counterparts.
Re:The Future of Developing Firefox Add-ons by wldcordeiro on Friday August 21, 2015 @12:53PM (#10098749)
They'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.
Re:The Future of Developing Firefox Add-ons by Tobu on Friday August 21, 2015 @02:25PM (#10099338)
They'll probably be less broken, with a proper API: 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.

Re:The Future of Developing Firefox Add-ons by the8472 on Friday August 21, 2015 @11:14AM (#10098030)
> 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.

Re:The Future of Developing Firefox Add-ons by sp332 on Friday August 21, 2015 @11:26AM (#10098102)
I don't know if that means that they will be disallowed, or just maybe broken.
Re:The Future of Developing Firefox Add-ons by the8472 on Friday August 21, 2015 @11:47AM (#10098258)
Mozilla 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.