Rendered at 02:25:38 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
AngryData 19 hours ago [-]
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.
mossTechnician 10 hours ago [-]
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.
highspeedbus 9 hours ago [-]
I still hold a grudge over the change from Photon to Proton theme. It should be easier to customize this.
jasomill 2 hours ago [-]
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).
quertyrecord74 16 hours ago [-]
the day firefox execs took private jets to meeting, I knew it can never be fixed. surprised still the downfall is not reached bottom
ThePowerOfFuet 11 hours ago [-]
When was this? Where can I read more about it?
kbelder 9 hours ago [-]
I added
border-radius: 0px !important;
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?
You also have to toggle "toolkit.legacyUserProfileCustomizations.stylesheets" to true in about:config
hxugufjfjf 9 hours ago [-]
I did both. Still round.
Update: I figured it out. The article’s snippet has no selector. As rendered it’s just { border-radius: 0px !important; }, which is invalid CSS and gets ignored (the * was probably eaten by the blog’s formatting). Use:
* {
border-radius: 0px !important;
}
justthisonceok 16 hours ago [-]
Firefox trying hard to get rid of good stuff, while keeping a bugzilla backlog of 15 years, what a surprise.
panja 13 hours ago [-]
I guess I'm the only one that likes this update...
microflash 13 hours ago [-]
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.
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.
At least choosing a different theme is the easiest it's ever been. Unlike the rounding, no CSS hacking is necessary.
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).
-----------------
Ok, found that you need a setting in about:config
Update: I figured it out. The article’s snippet has no selector. As rendered it’s just { border-radius: 0px !important; }, which is invalid CSS and gets ignored (the * was probably eaten by the blog’s formatting). Use:
* { border-radius: 0px !important; }
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.