4 ms·

Yes, it's a real shame that it seems like they don't even care about extensions anymore, and therefore forces me to stay on the older versions and miss out on t

Yes, it's a real shame that it seems like they don't even care about extensions anymore, and therefore forces me to stay on the older versions and miss out on the new and welcome improvements. I'd be more ok with their switch to web extensions if they had included more powerful API:s, even if they're not available in other browsers. My developer edition recently got upgraded to 57, and Greasemonkey stopped working. Reading what the developer writes it seems as they are going to rewrite the whole extension from scratch, with a lot of the functionality left out because it's no longer possible to do.

Vinnl 9y ago
If they hadn't deprecated the old extensions yet, the newest version would be pretty much the same as using the old version. This way, some people who don't rely on those extensions (I believe half of the users don't even run an extension at all?) can benefit from those improvements now, and you'll be able to do so later.
- rndgermandude 9y ago
  That's not true, the legacy extensions kept working w/ the project quantum stuff until mozilla broke completely unrelated stuff. E.g. Greasemonkey only broke because they renamed (not removed) a few things.
addicted 9y ago
Theyve built a whole development model reliant on extensions (Test Pilot). They’ve made tremendous progress on enhancing the extensions API. To say that they don’t care about extensions doesn’t seem to match the efforts you can see in the browser.
- baby 9y ago
  They def. don't care about Tree Style Tabs which is the reason number one a lot of people use Firefox.
  - callahad 9y ago
    There are functioning development builds of TST as a WebExtension. This is what it looked like last month: https://i.imgur.com/IBx8F6L.png https://i.imgur.com/IBx8F6L.png Not sure how that translates to "not caring." Edit: Oh, hey, look, the WebExtension version has been published: https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/ https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...
    - baby 9y ago
      1) It’s been constantly broken and re-fixed for years versions after versions 2) they do not reply to his requests or bugfiles 3) they could have made it a default in Firefox
      - callahad 9y ago
        And yet here it is, available and working as a WebExtension more than a month before legacy add-ons go away. The process may look opaque, but as far as results, I'm really not sure what more you want? We moved to WebExtensions specifically to fix the problem of constant breakage. Sure, it adds a layer of abstraction, but there's finally an explicit interface that we can commit to supporting. The legacy APIs were a monkeypatching free-for-all that prevented us from landing even minor improvements or refactors for fear of potentially breaking some add-on somewhere. Now that we have that interface, we can refactor without breaking add-ons.
        baby 9y ago
        And it's broken again :/ this time it just plain doesn't work and I can see the vertical tabs again. This hasn't happened in years...
      - oblio 9y ago
        Regarding 3, no they couldn't have. You're vastly overestimating how many people use it. I've seen 1 person using it, and I work in IT. Outside of IT the percentage is probably smaller...

Vinnl 9y ago

If they hadn't deprecated the old extensions yet, the newest version would be pretty much the same as using the old version. This way, some people who don't rely on those extensions (I believe half of the users don't even run an extension at all?) can benefit from those improvements now, and you'll be able to do so later.

rndgermandude 9y ago
That's not true, the legacy extensions kept working w/ the project quantum stuff until mozilla broke completely unrelated stuff. E.g. Greasemonkey only broke because they renamed (not removed) a few things.

addicted 9y ago

Theyve built a whole development model reliant on extensions (Test Pilot). They’ve made tremendous progress on enhancing the extensions API. To say that they don’t care about extensions doesn’t seem to match the efforts you can see in the browser.

baby 9y ago
They def. don't care about Tree Style Tabs which is the reason number one a lot of people use Firefox.
- callahad 9y ago
  There are functioning development builds of TST as a WebExtension. This is what it looked like last month: https://i.imgur.com/IBx8F6L.png https://i.imgur.com/IBx8F6L.png Not sure how that translates to "not caring." Edit: Oh, hey, look, the WebExtension version has been published: https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/ https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...
  - baby 9y ago
    1) It’s been constantly broken and re-fixed for years versions after versions 2) they do not reply to his requests or bugfiles 3) they could have made it a default in Firefox
    - callahad 9y ago
      And yet here it is, available and working as a WebExtension more than a month before legacy add-ons go away. The process may look opaque, but as far as results, I'm really not sure what more you want? We moved to WebExtensions specifically to fix the problem of constant breakage. Sure, it adds a layer of abstraction, but there's finally an explicit interface that we can commit to supporting. The legacy APIs were a monkeypatching free-for-all that prevented us from landing even minor improvements or refactors for fear of potentially breaking some add-on somewhere. Now that we have that interface, we can refactor without breaking add-ons.
      - baby 9y ago
        And it's broken again :/ this time it just plain doesn't work and I can see the vertical tabs again. This hasn't happened in years...
    - oblio 9y ago
      Regarding 3, no they couldn't have. You're vastly overestimating how many people use it. I've seen 1 person using it, and I work in IT. Outside of IT the percentage is probably smaller...