Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Really dirty rendering after relaunch #161

Closed
stefanhoth opened this issue Jun 19, 2014 · 2 comments
Closed

Really dirty rendering after relaunch #161

stefanhoth opened this issue Jun 19, 2014 · 2 comments
Labels

Comments

@stefanhoth
Copy link
Contributor

I may be late to the party but the relaunched site has a really bad rendering on Chrome 35 ( Windows ).

dirty_ots

@stefanhoth stefanhoth added the bug label Jun 19, 2014
@Ivoz
Copy link
Member

Ivoz commented Jun 20, 2014

@stefanhoth to note, please remember in all issues you make online to use clear language. What isn't clear to me is what exactly you mean by "dirty rendering" and "really bad rendering". Giving clear descriptions of exactly what's broken makes things unambiguous for everybody and ensures everyone is talking about the same thing.

Anyway, I'm guessing by this you might mean the unaliased rendering of fonts, but this issue is not infact new, it has been present for a great while, probably over a year. So maybe you mean something else?

If you do mean that, then it is unfortunately a bug specific to Chrome on Windows; it uses an old text rendering API (GDI) which isn't up the task of nicely anti-aliasing custom web fonts. It's hard to find a satisfactory workaround that applies CSS to only Chrome on Windows (unfortunately, as opposed to IE!). This would also then be a duplicate of #96

@stefanhoth
Copy link
Contributor Author

@Ivoz yes, I meant this issue and sorry for not making myself clear enough.

Closed as a duplicate of #96. (But it's more apparent with the new design)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants