3 ms·
> But it shouldn't really be an issue because of progressive image loading. At the very least, the text should always load first. Back when I had dialup, it cou
by Cyberdog 11y ago
> But it shouldn't really be an issue because of progressive image loading. At the very least, the text should always load first. Back when I had dialup, it could take ages for a page to load completely because of the images. You could watch them slowly fill in, line by line. And if you didn't care about them, you could ignore them.
I remember the dial-up days too. You could only read the text around the images while waiting for the images to load.
Now we sort of have the opposite problem when pages use huge unnecessary web fonts; you can only look at the images while waiting for the font to load so the browser can render the text.
(I found sending fonts.googleapis.com to 127.0.0.1 in my hosts file helped a lot in that regard. Wish my browser had an option to block all fonts, though.)
FLIF looks like cool tech, but I won't hold my breath until it has wide browser support.
- Houshalter 11y agoI will agree with you that web fonts are the stupidest thing ever. There seems to be some extensions to block them, though I haven't tried it yet. I don't know why the text isn't rendered normally until the font downloads, or why common fonts aren't cached locally.
- izacus 11y agoBecuase web developers deliberately work around that (color text white or hide it) so the text doesn't display until font is loaded to avoid the text pop. Of course that makes the site unusable if font CDN is down.