Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Sa 04.05.2024 00:00:18 2.881 0 366.106 127,1 Toot Café 4.2.8 500 Fr 03.05.2024 00:00:20 2.881 0 366.097 127,1 Toot Café 4.2.8 500 Do 02.05.2024 00:00:11 2.881 0 365.953 127,0 Toot Café 4.2.8 500 Mi 01.05.2024 00:00:29 2.881 0 365.851 127,0 Toot Café 4.2.8 500 Di 30.04.2024 00:00:24 2.881 0 365.718 126,9 Toot Café 4.2.8 500 Mo 29.04.2024 00:00:21 2.881 0 365.584 126,9 Toot Café 4.2.8 500 So 28.04.2024 00:00:20 2.881 0 365.568 126,9 Toot Café 4.2.8 500 Sa 27.04.2024 00:00:14 2.881 0 365.482 126,9 Toot Café 4.2.8 500 Fr 26.04.2024 00:00:21 2.881 0 365.352 126,8 Toot Café 4.2.8 500 Do 25.04.2024 00:01:18 2.881 0 365.235 126,8 Toot Café 4.2.8 500
Adrian Roselli (@aardrian) · 12/2017 · Tröts: 17.248 · Folger: 2.481
Sa 04.05.2024 01:24
It’s not wrong. But it’s not right, either.
“Creating Fluid Typography with the CSS clamp() Function”
https://www.sitepoint.com/fluid-typography-css-clamp-function/#:~:text=setting%2016px%20(or%20whatever%20value%20you%20want)%20as%20the%20root%20font%20size
It is, however, nice to see that my advocating for less broken fluid type approaches has paid off, even if the handwavy ‘accessibility’ explanations don’t point to my post that first raised them. It’s cool, it’s only my ego (and detailed explanations with examples).
Heading: “A note on accessibility.” Then some code examples, then I highlighted: “I’d recommend defining any font values that you leverage within your code using rem. This is standard best practice these days, and shouldn’t really have to be explained further than the fact that setting 16px (or whatever value you want) as the root font size and using rem as a relative unit of measurement to define font sizes is good for accessibility and user experience.”
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Web