Hopefully most of the missing extensions will be developed sooner rather than later. I have 15 extensions installed, 14 of which are "Legacy". The most critical one, Tree Style Tabs, has been converted. That was the key blocker that prevented me from seriously using Chrome. But many more remain; Cookie Controller, RefControl, some kind of Classic Theme Restorer equivalent (to get a menu bar back for Bookmarks, at a m…
Unfortunately, I don't think theres ever going to be a Classic Theme Restorer equivalent that works going forward. https://bugzilla.mozilla.org/show_bug.cgi?id=1328244
Firefox 57.0 Released
81–90 of 836 posts
Re: Firefox 57.0 Released
#82I just upgraded. It completely changes the chrome of the browser on OSX and it is _absolutely hideous_. There are a lots of unnecessary animations that I find very jarring. I don't know if there's a way to change it back yet. UPDATE: There is a "Customize Firefox" button which allows modifying the theme, which fixes the colors, but not the shape of the tabs or the animations. UPDATE: In about:config, you can disable…
Re: Firefox 57.0 Released
#83Hopefully most of the missing extensions will be developed sooner rather than later. I have 15 extensions installed, 14 of which are "Legacy". The most critical one, Tree Style Tabs, has been converted. That was the key blocker that prevented me from seriously using Chrome. But many more remain; Cookie Controller, RefControl, some kind of Classic Theme Restorer equivalent (to get a menu bar back for Bookmarks, at a m…
Tree Style Tabs was the only blocker for me, and I was amazed that it was possible to recreate under the new API. I use both Firefox and Chrome, but for very different purposes. In Chrome, I have 20-50 tabs spread across two windows. In Firefox, 400+. Tree Style Tabs is necessary for how I use Firefox. My backup plan was staying on an older version, possibly indefinitely.
Re: Firefox 57.0 Released
#84Hopefully most of the missing extensions will be developed sooner rather than later. I have 15 extensions installed, 14 of which are "Legacy". The most critical one, Tree Style Tabs, has been converted. That was the key blocker that prevented me from seriously using Chrome. But many more remain; Cookie Controller, RefControl, some kind of Classic Theme Restorer equivalent (to get a menu bar back for Bookmarks, at a m…
In time, they say, they will bring back the various APIs for the extensions (although it's still "might" and there's no timeline yet) - so in the meantime, if you liked FF for it's customisation, we just have to suck it up. It's similar to when Ubuntu moved to Unity and attracted all the new users but pissed off all the existing userbase. We should expect a big backlash when all the linux repos get updated and the power users release they have a degraded experience.
Re: Firefox 57.0 Released
#85It's supposed to be faster, but when I open developer-tools and click on "Inspector", it takes almost 5 seconds to paint. EDIT: Okay, tested again; it depends heavily on the website you do this on.
Re: Firefox 57.0 Released
#86Hopefully most of the missing extensions will be developed sooner rather than later. I have 15 extensions installed, 14 of which are "Legacy". The most critical one, Tree Style Tabs, has been converted. That was the key blocker that prevented me from seriously using Chrome. But many more remain; Cookie Controller, RefControl, some kind of Classic Theme Restorer equivalent (to get a menu bar back for Bookmarks, at a m…
It's worth noting that most legacy extensions still actually work. You just need to enable them.
Re: Firefox 57.0 Released
#87Hopefully most of the missing extensions will be developed sooner rather than later. I have 15 extensions installed, 14 of which are "Legacy". The most critical one, Tree Style Tabs, has been converted. That was the key blocker that prevented me from seriously using Chrome. But many more remain; Cookie Controller, RefControl, some kind of Classic Theme Restorer equivalent (to get a menu bar back for Bookmarks, at a m…
The WebEx Tree Style Tabs is markedly inferior to the "Legacy" version. It is simply an integral and indispensable part of my workflow, so much that I can't even fathom browsing without it. I guess I'll stay on 56 for a while.
Re: Firefox 57.0 Released
#88It's supposed to be faster, but when I open developer-tools and click on "Inspector", it takes almost 5 seconds to paint. EDIT: Okay, tested again; it depends heavily on the website you do this on.
Less than a second here. Yes, I can see it paint, but it's nowhere near 5 seconds. And I'm on a base model Thinkpad T440, hardly a speed machine these days.
Re: Firefox 57.0 Released
#89Re: Firefox 57.0 Released
#90I just upgraded. It completely changes the chrome of the browser on OSX and it is _absolutely hideous_. There are a lots of unnecessary animations that I find very jarring. I don't know if there's a way to change it back yet. UPDATE: There is a "Customize Firefox" button which allows modifying the theme, which fixes the colors, but not the shape of the tabs or the animations. UPDATE: In about:config, you can disable…
Do you have any specific examples?
The top bar is also black-ish now rather than the system grey. This looks particularly bad with the new "blue" highlight indicator. The tabs are all square rather than rounded. It all looks pretty hideous.