Does anyone feel that this new UI brings notable improvement? I don't think it is much worse, other than taking some extra vertical space but for the most part my reaction is "meh". I feel like these resources could have been spent much better in other parts of the browser. Am I missing some reason why this is worth the investment?
I don't mind the changes. I had to look a bit for the new location of the screenshot tool. It's now a button you can add to the toolbar. Otherwise, the changes are mostly pretty subtle and they make sense to me. They have UI people and designers. So they are going to be doing UI and design things. IMHO they are better off with these people than without. Browsers are very competitive. So, keeping the UI fresh and up t…
Firefox Release 89.0
471–480 of 487 posts
Re: Firefox Release 89.0
#472Re: Firefox Release 89.0
#473Still can't use it. The tabs have the close button on the wrong side, for me as a Mac user. And yes, this is a serious issue. So far Opera and Vivaldi got it right. Brave and Firefox lack behind here.
Why do you even need the close buttons on tabs? I close them with the middle click.
Re: Firefox Release 89.0
#474Earlier quoted context omitted.
Which addon do you use?
Tree Style Tab and some custom css to hide top tab panel
Mine looks like:
@-moz-document url("chrome://browser/content/browser.xul") { #TabsToolbar { visibility: collapse !important; } }
Re: Firefox Release 89.0
#475I'm a long time user of FF. I really don't like the UI changes in this upgrade, but setting: "browser.proton.enabled" to false "browser.uidensity" to 1 (while using the `System Theme`) Seems to have done the trick, so, I can just ignore the UI changes (which is great)... fingers crossed in that this keeps working in the future. UI changes are very much subjective, so, I think that it's great that some people like the…
Settings probably will be removed as soon as possible. Take a look at UI customizations that can be made using userChrome.css : https://www.userchrome.org/firefox-89-styling-proton-ui.html
Re: Firefox Release 89.0
#476Earlier quoted context omitted.
Don't be over dramatic. It's still tabs and an URL bar, there's nothing to adjust to.
Even the back button is wrong in the new version. Previously it spanned up to the left edge of the window. Now it's moved to the right, lacks immediate feedback and then it is drawn to the right with some new empty space for no reason but to make it harder to hit the back button, the most used button of the interface. The visual cue with the circle around it is also gone. Even the lines used to draw the arrow are thi…
Most of the time, it doesn’t take too long to get used to the interface changes – though I think a lot of such changes are superficial (make it look shiny and new) and I’d rather developer resources were used elsewhere. It’s not like there are no open bugs on Bugzilla. Also, I wonder if they do any testing of the UI changes with an older demographic.
Re: Firefox Release 89.0
#477Earlier quoted context omitted.
I personally think it's a big improvement over what it was before -- on macOS at least. On macOS, Firefox had always felt a little bit off. Nothing too egregious, but just enough to make it slightly unpleasant (like the non-native context menus). I feel like that has been resolved in this update.
Try streaming a call on MacOS... you'll feel a bit off. 40x the energy usage vs Safari. It's atrocious. Laptop gets to silly high temps, has to be bad for battery life... But I'm sure glad we have some new popup confirmation windows. Cool. EDIT: I use FF on my Mac as my primary browser. Just so frustrated at how little fucks they give about performance and battery usage.
Re: Firefox Release 89.0
#478It is fascinating how much negative feedback the redesign is getting on HN. I am using it on Mac and Windows now and I think it is great! The Firefox design always felt very dated compared to Chrome, Safari and Edge. Not the case anymore :)
Re: Firefox Release 89.0
#479I'm a long time user of FF. I really don't like the UI changes in this upgrade, but setting: "browser.proton.enabled" to false "browser.uidensity" to 1 (while using the `System Theme`) Seems to have done the trick, so, I can just ignore the UI changes (which is great)... fingers crossed in that this keeps working in the future. UI changes are very much subjective, so, I think that it's great that some people like the…