FireGestures -> https://addons.mozilla.org/en-US/firefox/addon/foxy-gestures...
SDC -> https://addons.mozilla.org/en-US/firefox/addon/cookie-autode...
It'll take a bit for the new generation of extensions to fully replace the old one, but it's happening.
I'm not sure what browser I'm going to use to be honest. All the hotkey browsers are buggy as hell since they use qtwebkit, webkitgtk, qt-webengine and whatnot. Chrome has extensions like cvim which sort of work, but they suffer from issues like not being able to properly hook keys and properly notify the user about the state you're in making me frequently make mistakes on what I want to do. As the sibling said a poor imitation of what was possible before.
If firefox just immitates chrome, what's the point in having it? How about trying to eat some of IE's lunch by making enterprise customization a first class citizen? But then again not sure if that matters. And yes I'm aware of GPO, but calling that first class citizen is disingenuous at best.
The more I read, the more APIs turn out to be missing or buggy, making it impossible for add-ons to be made (if the developer is active in the first place). I just don't understand this. Firefox was built on the extendible principle and they're now going back to "v0.2 beta" in that regard.
This process should have taken years to mature the new APIs before dropping support for the old method.
Notice that major bump in August 2016 and after? Firefox 48 was released on the 2nd August 2016. This was the first release to ship the new multiprocess architecture. And this new architecture also already required breaking all extensions.
They could not have shipped it this early without knowing that the switch to WebExtensions will cut off the multiprocess-incompatible extensions.
And they needed to get multiprocess shipped. Had that graph continued as in the half year before that, we would now have negative user numbers.