I was baffled by the CSS syntax but nodding along thinking "I guess CSS changes a lot each year" until I did a double take when I read @google-font. Turns out the author makes https://css-doodle.com/ which adds its own functionality to CSS
the first of their "two more examples" images tells me that the 𖤛 in the font they used has an improperly closed path in the top right extreme point
Are these all improperly closed paths? I keep looking at these examples and seeing the same kind of bug being amplified in each subsequent outline causing jagged outlines that aren’t representative of the underlying characters. You’re saying there’s bugs in the vectors of the font they’re using and that’s what’s causing all of them?
boehs | 10 days ago
I was baffled by the CSS syntax but nodding along thinking "I guess CSS changes a lot each year" until I did a double take when I read
@google-font. Turns out the author makes https://css-doodle.com/ which adds its own functionality to CSSdahjelle | 9 days ago
I was started by
@google-font, too. It looks like CSS custom functions are in the pipeline, though not widely supported yet.scruss | 9 days ago
the first of their "two more examples" images tells me that the 𖤛 in the font they used has an improperly closed path in the top right extreme point
winsec | 9 days ago
Are these all improperly closed paths? I keep looking at these examples and seeing the same kind of bug being amplified in each subsequent outline causing jagged outlines that aren’t representative of the underlying characters. You’re saying there’s bugs in the vectors of the font they’re using and that’s what’s causing all of them?