also known as the default font size in browsers, don't you dare override the user's preferred font size for body copy, scale everything else in units of rem instead.
What was a regular border, eventually becomes a half-circle.
I did mean font sizes though. :)
In practice it doesn't really mean much outside of blog-like text so when doing layouts it's more of just a standard everyone agrees on using everywhere because it's easier to stick to one for consistencies sake and it does the job. I don't think many frontend devs ever test zooming text using a browser anyway, their main concern is variations in screen sizes, basically device variation not manually zooming text. But I get the arguments to limit it to text.
I've never seen a CSS framework that's good. (Unless you count https://simplecss.org/, but that's of very narrow usefulness.) They're all made by the kinds of people who don't understand web technologies, and seek to hide them behind a layer of abstraction so they don't have to think about them any more. Unfortunately for them, there's a reason the web's how it is. Some of it's backwards-compatibility, but most of it is that a large group of very clever people failed to find a way to make it any simpler without breaking something important; and so, the framework people tend to break important things.
If you find yourself reaching for something like Tailwind or Bootstrap, just use inline style attributes. It's easier for everyone involved.
Wrt Tailwind I still have not used it enough to decide whether it is good™ but it is not that different from writing inline styles.
Apart from optional plugins it is more like a CSS preprocessor than a framework (every class expands to one or few CSS declaration)
The most frameworky features it has is that it predefines CSS variables to allow further customization
A crude "not that different from writing inline styles" classy framework just makes it harder to refactor your CSS in future, because it's all tucked away under incomprehensibly-named CSS classes, and there are otherwise-useless <div>s all through the HTML.
For handwritten html I believe that tailwind has significant downsides (unless you abuse @apply), but that the case I focus on.
I should have mentioned that I believe tailwind to be applicable only if you have some strong templating support
> Use <style scoped='scoped'> in the <body>
This seems to have been removed from everywhere since at least 2017
I’d bet you that 98+% of users don’t even know you can change the browser font size. For that overwhelming majority of users the size reported by their preferences and their actual preferences do not necessarily align. This is not a defence of setting smaller-than-16px font sizes, but it is a defence of setting larger sizes if testing shows it improves user experience.
See: HN, that sets a "10pt" font size, otherwise known as 13px.
At least they have a reason and it fits for me. :)
body {
font-size: larger;
}
.comment, .default, .comhead {
font-size: 14px;
}
.subtext, .pagetop {
font-size: 13px;
}
.title {
font-size: 16px;
}
It's not the prettiest CSS or the most well done, but it works and it's better than the defaults imo.The users that need that to be able to read (e.g. vision problems) definitely do know that. It's about accessibility
https://community.qbix.com/t/qbix-websites-loading-quickly/2...