3 ms·
You probably only saw the cursive backup font and not the intended Roboto font that the page actually uses (which took about half a second to load for me); here
by sestep 1y ago
You probably only saw the cursive backup font and not the intended Roboto font that the page actually uses (which took about half a second to load for me); here's a snippet from the CSS:
font-family: "Roboto", "Underdog", cursive, -apple-system, BlinkMacSystemFont,
"Segoe UI", Helvetica, Arial, sans-serif, "Apple Color Emoji",
"Segoe UI Emoji", "Segoe UI Symbol";
- adastra22 1y agoSite really needs to drop the completely unreadable backup font.
- dangus 1y agoCommenters need to stop complaining and hit the reader mode button on their browsers.
- nosioptar 1y agoReader mode isn't an option for me on this page using Firefox mobile. The better solution is that web devs and designers should either stop changing fonts or learn how to do so without making peoples' eyes bleed.
- skeledrew 1y ago> Reader mode isn't an option for me on this page using Firefox mobile. It is for me. Page was great when I opened it in Telegram browser (my default) though, and then I saw the crazy when I opened in Firefox.
- bravesoul2 1y agoUA's FTW.
- adastra22 1y agoNot all browsers have a reader mode. And for the record I usually don’t like these design-related comments, but it was literally unreadable. Like some sort of 17th century chicken scratch cursive.