How much harder is it to discover the ability to write custom CSS? Do we know that Firefox won't apply the same logic to that feature?
given this trend of removing little usability and customization abilities here and there, one can only assume the custom CSS will be removed as well. especially seeing as its label has "legacy" right in it's name: toolkit.legacyUserProfileCustomizations.stylesheets
they'll give some reason like "only 1% of users use it" or, "it'll take too much time to make it work with our new, annual UI redesign/overhaul"
that being said, I'm sure someone (either on github or on reddit in /r/FirefoxCSS) will have the necessary custom CSS written to reproduce as soon as the version removing it hits the stable release
Of course, every major redesign of the browser breaks the CSS for multi-row tabs and I need to find people who have fixed it and hack it back together. One of these days they'll probably break it completely and I'll switch to another browser.
I miss using Firefox, but I don't miss the dread-churn of notices like this.
Brave seems more like the "consumer disliking ads/google" choice.
In all seriousness, very few power-user browsers exists, to the point where QuteBrowser is the only fully-functional one I can think of... Which is sad.
Brave is "just" a completely regular browser owned by someone else + a few bonus features.
I want more people using Firefox, that'd be awesome, but Mozilla could really do with more compelling arguments for changes like these, and while they're at it a better approach to engaging with the community.