4 ms·
I don't like how they altered the font on their webpage to something that is so thin that strokes are only visible as subpixels. Glad the API docs use a readabl
by currysausage 11y ago
I don't like how they altered the font on their webpage to something that is so thin that strokes are only visible as subpixels. Glad the API docs use a readable normal-weight font instead.
If you need to visually "hide" the text in order to make it look "clean," you're doing typography wrong.
- epmatsw 11y agoI wonder if they changed it since this comment. It's about the same as HN for me now.
- freehunter 11y agoI thought it was odd how the page loads with normal text, then blinks for a second and the text gets 2x thinner. If it takes time to load your fonts, you're doing fonts wrong.
- xigency 11y agoI'm fine with the fonts, I just noticed when I middle-clicked to scroll the page, the page moved like it was underwater. Really unnecessary for a text document. The offending CSS is: html { scroll-behavior: smooth; } Only noticing this issue in Firefox.
- nilliams 11y agoAs that is a CSS spec, the implementation of which you don't like, it's the browser that's offending, not the CSS.
- xigency 11y agoSure, if you like to read while you're wading through butter. It's a usability thing. Anyways, they do it on their whole site, and it's more cohesive on the other pages. It's better to view the release notes in readerview I guess.