Why no more icons in menus? :(
They're making you agitated, apparently: " Cohesive, calmer visuals: Lighter iconography, a refined color palette, and more consistent styling throughout. "
[deleted]
Firefox Release 89.0
91–100 of 487 posts
Re: Firefox Release 89.0
#92Earlier 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.
Yeah, not only did the old tab design have an indicator what tab was playing audio, it actually was more helpful since the audio indicator did not take over the favicon. I could clearly see that it was YouTube's favicon next to the speaker icon - now I only see the speaker icon.
Re: Firefox Release 89.0
#93Does 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 found the UI changes on windows, while being fairly minor, being much nicer than what was before. It's added a lot of polish without affecting my workflow in any ways.
Re: Firefox Release 89.0
#94> "We’ve redesigned and modernized the core experience to be cleaner, more inviting, and easier to use." Why does the UI change with every single Firefox release? I find myself having to re-adjust every time a new update is shipped. What's wrong with having a consistent experience that survives for more than 6 months? It's just a URL bar, and a bunch of tabs. Just leave it be already.
idk. I kind of trust that the firefox team has competent designers that know what they are doing. Perhaps they found some issues in usability studies, tested a redesigned that fixed those, and sent the patch in the current release.
Re: Firefox Release 89.0
#95When was the last time a UI update didn't add padding?
Eventually apps will be nothing but padding!
Re: Firefox Release 89.0
#96Does 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 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
#97> "We’ve redesigned and modernized the core experience to be cleaner, more inviting, and easier to use." Why does the UI change with every single Firefox release? I find myself having to re-adjust every time a new update is shipped. What's wrong with having a consistent experience that survives for more than 6 months? It's just a URL bar, and a bunch of tabs. Just leave it be already.
I also frequently wish developers would leave well enough alone, but what changes are you referring to? I don't remember big changes since Firefox 57 and even those took me maybe thirty seconds of adjustment.
This recent update seems more like a very minor reskinning than anything that would require adjustment.
Re: Firefox Release 89.0
#98Does 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 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.
They stopped trying to make menus even look native on other systems.
Re: Firefox Release 89.0
#99Looks like this is the first stable version with their renewed UI? Downloading.
Oh dear God, is it like the mobile version? I need to turn off updates asap and test it first. I was willing to give it more time on Android, but it would randomly stop loading pages and that was the last straw. I begrudgingly use Chrome now :/
Tell me about it. The newer Android Firefox UX is so bad I'm forced to stay on version 68. I can't use other browsers since extensions are core to my web browsing experience (especially userscript managers). Maybe once a year I'll try out the latest version to see if they've ironed out some of the problems.
Re: Firefox Release 89.0
#100Does 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?
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 accident. Someone decided that they should hire them.