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

I think it would be easier to evaluate this font if the page were not using

  -webkit-font-smoothing: antialiased;
which IMO really should be a last resort, and with this particular colour combination triggers halos that detract from readability.


I don't see that anywhere in the page source. And when I try to manually inject that css it says it's an invalid property name.

For context, I'm using Firefox on Linux. Also I haven't done any real front-end work in 10 years, so forgive me if I am missing something obvious here.


It's an invalid property in Firefox, yes, so you're not seeing its effects.

Firefox may simply not display it in the inspector, I'm not sure!

Anyway it's in app.css on line 185; it's applied as a body style. Looks like it comes from Zurb Foundation (ugh).


Thanks for the response. I see it is not standard CSS, and that Firefox has a different property name to set this.

https://caniuse.com/?search=-webkit-font-smoothing


The fact that I haven't done any serious work involving hinting with this font may have something to do with this issue as well. I'll have to look at this later.


My word, that is so much nicer. I wish people would stop doing this.




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

Search: