Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Well it is experimental for a reason.

As quoted from the bug report

> The webkit-font-smoothing css property is, contrary to the summary, still working. It is still respected, as no lcd font smoothing is being applied. However, the bug where it also affected the weight of the text as a side effect has been fixed.

Though it's worth noting they are looking into whether the purpose (and thus the function) of this particular property should be adjusted.



It actaully doesn't have much to do with -webkit-font-antialiasing as a css extension, and much more to do with how chrome is handling font rendering in general. v22 was a big, big step backwards.

Designers and typographers are pissed. Even if it's "right" as the chromium devs seem to insist, it doesn't change the fact that fonts look like shit, and don't look like type designers intended them to render.


Is this a case where the bug presents a better solution than the intended design?

Your last sentence is reassuring that the developers appreciate this too.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: