Wow. This is a significant UX improvement for MacOS users! I might try FF as my daily personal browser in lieu of Safari.
Overscroll and (to a lesser extent) native context menus are huge to me.
Firefox Release 89.0
101–110 of 487 posts
Re: Firefox Release 89.0
#102Earlier 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.
Since you've already mentioned it - I hear that Firefox has non-native context menus all the time, but for the life of me couldn't tell any difference between "native" and "non-native" context menus. Anybody has any proof/example of this?
Re: Firefox Release 89.0
#103Earlier quoted context omitted.
In about:config, set "browser.proton.enabled" to false. I don't know if this will work in future versions, but it works in v89.
It won't work for long. Better start looking for userChrome.css fixes.
The only one I've seen so far is Firefox-UI-Fix. In my opinion, it looks like it's halfway between the old and new UI.
https://github.com/black7375/Firefox-UI-Fix/
Re: Firefox Release 89.0
#104Earlier quoted context omitted.
There's more info on tabs now, e.g. when a tab is playing audio. And it apparently was also triggered by observing that people didn't really know they could move tabs around and manipulate them in other ways, which does seem more obvious now that they're "detached" from the content. That said, I won't really notice since I use the Sidebery extension for vertical tabs. But I've got a separate profile running to isolat…
> more info on tabs now, e.g. when a tab is playing audio. That was present for a few versions now. Playing tabs had the audio icon which could be used to mute/unmute.
True - my only gripe with it is that video icon is in the same place - if I have 5 YouTube tabs, 1 playing, that one with audio icon is very hard to distinguish from the other 4 with video icons. Not sure if video icon is useful to some people at all, especially since it's shown even if video is not actively playing.
Re: Firefox Release 89.0
#105Love it. Fresh new sleek look. Firefox needs to be sexier to attract more than just the tech crowd.
Re: Firefox Release 89.0
#106does this 89.0 have the annoying update now dialog, or at least a setting to block it? In version 72.02 that I am using it pops up with every new tab and there is no setting to block it.
Re: Firefox Release 89.0
#107Earlier 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.
Since you've already mentioned it - I hear that Firefox has non-native context menus all the time, but for the life of me couldn't tell any difference between "native" and "non-native" context menus. Anybody has any proof/example of this?
Right-click on a word in Chrome/Safari (or really any other macOS application) and right-click on a word in old Firefox.
Re: Firefox Release 89.0
#108I was worried last year (I think it was last year...) when Mozilla laid off a bunch of people that Firefox would be a casualty. Thankfully that doesn’t seem to be the case!
Is this irony? A lot of the fired developers worked on the engine and all the surrounding levels below the UI, there are bugs lasting years in the current engine, but this is the UI lipstick change nobody needed anyway but its convenient for the management to demonstrate that "they" did "something". A tab that doesn't look like a tab but like a button. Progress!
You do realize there are plenty of more technical changes in Firefox from release to release? Eg, per site process isolation was merged recently.
Re: Firefox Release 89.0
#109Earlier quoted context omitted.
The UI/UX team that works on this likely aren't backend coders. They can either fire the team or put them to use, but reassigning them random C++/Rust tasks probably isn't possible.
To be perfectly blunt it doesn't matter what a team is doing. They paid $X million to "design resources" and directed those resources at the redesign featured in this release. Instead they could have paid that to backend, other UX initiatives, the extension team, the privacy team... I understand that you can't swing resources around freely in the short term but you don't have a bunch of designers sitting around by ac…
You're right the money could be spent elsewhere. But calling people resources is rude to put it mildly.
Re: Firefox Release 89.0
#110How much research was done on the UI changes improving useability? I can't determine this...
You may want to check out these tickets [1][2]. The latest comment in the second link nails it for me.
> I don't understand this decision. First the removal of compact mode was motivated because is has bad discoverability. Then community raise its voice to say that not what it wants. And the answer is to make the setting even less discoverable…
> Of course is won't be used if it is less and less discoverable. And this decision break the meaning of doing telemetry on compact mode altogether, how are we going to mesure if people prefer Proton normal vs Proton compact if they don't even have the option showed at all???
> Please keep support on compact mode, don't let it rot and broke