3 ms·

Yes, that is wrong :) So what's happening is that the extension stuff is going to be standardized, and that standard will be closer to Chrome's model. However

Yes, that is wrong :) So what's happening is that the extension stuff is going to be standardized, and that standard will be closer to Chrome's model. However, this doesn't mean that functionality will be lost -- this is the key bit of confusion around this that's causing all the resentment. Instead, the protocol will be extended. 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. Functionality from Firefox's API will only be removed when there is something on the webextensions side that gives the same abilities. The current system lets plugin developers directly hook into Firefox source, which means that theoretically any change is a breaking change. Architectural overhauls like electrolysis were impeded by this too. Instead, the desire is to switch to a proper API that is separate from the inner functionality; which is basically a core principle of API design. Chrome already does this -- the API is limited -- but the generic model is the right one. The plan is to do something similar in Firefox, with a much larger API (eventually) than what Chrome has. At first, probably just the Chrome API will be implemented, but IIRC regular firefox addon APIs will not be removed until the corresponding APIs exist in the webextensions format. This will mean that authors of old addons may need to put some work into it to make it work again (which they had to do anyway for electrolysis, really). Also, obscure addons using very random internal APIs may also break entirely. But for the most part the average addon user shouldn't notice anything.

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 ago
      I 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? :)
kuschku 10y ago
Can I still modify the entire UI with an addon, for example, to add tab previews on hover? Or are you guys going to implement every single incompatible addon yourself?
- Manishearth 10y ago
  I don't know, but I think the answer is "it depends on how many people want that". Sounds like an API that would be part of the API tree style tabs would need anyway.

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 ago
    I 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? :)

kuschku 10y ago

Can I still modify the entire UI with an addon, for example, to add tab previews on hover? Or are you guys going to implement every single incompatible addon yourself?

Manishearth 10y ago
I don't know, but I think the answer is "it depends on how many people want that". Sounds like an API that would be part of the API tree style tabs would need anyway.