3 ms·
> Yes, that is wrong :) Fantastic news, thanks! > The intention is so that almost all extensions, especially the popular ones like tree style tabs, will keep
by reitanqild 10y ago
> Yes, that is wrong :)
Fantastic news, thanks!
> The intention is so that almost all extensions, especially the popular ones like tree style tabs, will keep on working; however they will need to be written to work with the new APIs.
This sounds doable.
> but IIRC regular firefox addon APIs will not be removed until the corresponding APIs exist in the webextensions format.
Again, this should sort it.
My worry was if we would be left with only chrome-like or worse browsers - for me Firefox currently plays in different league.
Edit: you possibly see why I and others were mistaken; you are the first one I know that has explained this. Feel free to tell relevant people why we misunderstood so we can clear up the FUD.
- Manishearth 10y ago> Edit: you possibly see why I and others were mistaken; you are the first one I know that has explained this. Feel free to tell relevant people why we misunderstood so we can clear up the FUD. Right. There's been a lot of FUD on this and not enough has been explicitly said. I'm pretty sure this was clearly stated in some places, but FUD spreads easily :) Maybe I can convince someone to write something about it.
- rhelmer 10y ago> Maybe I can convince someone to write something about it. You should come chat in #webextensions, if we can identify where messaging is falling down and fix it this would be great! I think one thing missing right now is having good "release criteria" for WebExtensions (like we did for e10s) - I don't think implementing every single API that's available to old-style extensions right now is a tractable problem (since it's "every internal API", all the way up to executing arbitrary commands).
- Manishearth 10y agoI had a chat in #devrel :) yes, of course, its not every internal API but the bottom line is that most extensions should still work, right? :)