Nice, I was mildly annoyed with the UI change. It takes longer for me to see which tab was active with the style and I didn't really find it any more pleasing to look at.
It's relatively good news that, in my opinion, the Default theme is the biggest whiff with the design overhaul. If Mozilla had just chosen a different option like a basic blue, it may have gone over a bit better.
At least choosing a different theme is the easiest it's ever been. Unlike the rounding, no CSS hacking is necessary.
None of this had to happen if Google didn't have to change design systems every year like they come up with a new messaging app every year.
Google's Fisher-Price-ificiation of software UX is bad and should have never spread. Material Design leading to Material 3 Expressive with the giant empty space and giant gaping voids that are buttons was an absolute mistake.
And then it spread to the rest of software, enshittifying along the way.
I was also fine with FF 156 version of Nova where compact mode was really compact with vertical tabs and rounding was restrained enough. With FF 157 they have added more padding to vertical tabs to compensate for close tab icon on rounded favicons, menu borders are so rounded they clip menu items, PIP min size lock has been removed so you can minimize it to a popsicle, and so on. It seems like they skipped a lot of QA.
Is there a reason they can't offer the previous theme as an installable theme for the new theming system?
This would be a lot more convenient than putting it behind an about:config-only preference that you need to jump through hoops to sync (and that's more likely to be removed sooner than the new theming system).
to my user chrome as per the article, but it didn't seem to accomplish anything. I've restarted with no effect. I didn't have a custom userChrome.css file before, but the instructions were clear enough. Do you have to enable it or something?
I hate that we have to hover over elements to see the border that separates them these days. That and these thin disapearing scroll bars with no clicky arrow buttons. I feel I must be the only person that still wants to use those little arrows lol. Dont get me started on gray text on a white background. Accessibilty should always be #1.
20 comments
[ 3.2 ms ] story [ 38.5 ms ] threadAt least choosing a different theme is the easiest it's ever been. Unlike the rounding, no CSS hacking is necessary.
Google's Fisher-Price-ificiation of software UX is bad and should have never spread. Material Design leading to Material 3 Expressive with the giant empty space and giant gaping voids that are buttons was an absolute mistake.
And then it spread to the rest of software, enshittifying along the way.
This would be a lot more convenient than putting it behind an about:config-only preference that you need to jump through hoops to sync (and that's more likely to be removed sooner than the new theming system).
This is so desgusting.