3 ms·
> (The end user should apply their own CSS if wanted; I still remember the time when user styles were a first class feature built into all browsers. Hell, that
by TeMPOraL 5y ago
> (The end user should apply their own CSS if wanted;
I still remember the time when user styles were a first class feature built into all browsers. Hell, that 'C' in CSS - "Cascading" - was always there to allow styles to enhance/override prior styles, including allowing the user to override website's styling. Back before web designers ruined everything by making every web page into its own special snowflake, people thought users would have one or two default CSS sheets to choose from and apply to any webpage, the way we today think about "dark mode".
These days, we have to resort to using browser extensions. A well-known one is Stylus [0][1]. In a way, it's much better than old built-in user styles. But then, it's not built in. Still, it's a nice way to fix up some of the frequently visited websites.
--
[0] - https://github.com/openstyles/stylus https://github.com/openstyles/stylus
[1] - Mind the name, it's "Stylus", not "Stylish" - the latter used to be popular, but then it sold out and become another peace of surveillance capitalism detritus. Stylus is a GPLv3 fork of Stylish with data collection removed.
- mark_and_sweep 5y agouserChrome.css and userContent.css still work just fine in Firefox (though you have to enable toolkit.legacyUserProfileCustomizations.stylesheets in about:config first). I'm using them to (re-)style both the Firefox UI as well as some specific sites.