Roel Nieskens on Nostr: If a webfont doesn't support a character that's on the page, the browser will go down ...

If a webfont doesn't support a character that's on the page, the browser will go down its internal font stack until it finds a fallback font to render that character.

I thought this meant you could never see a webfont's .notdef "tofu" glyph.

But TIL that if you use a Private Use Area unicode value, the browser will try to render it in the first webfont on the stack, and if it can't, use *that webfont's* .notdef instead.

#typography #css