this problem occurs after chrome update (ver52). As I learnt, DirectWrite was removed on chrome://flags, therefore I didn't do anything to solve the problem.
Especially small sized fonts are render blurry and jagged. When I design a web page fonts really bother me.
I tried a lot of CSS tricks but no one solved the problem. (text-shadow, font-smoothing, transform3d, filter, zoom, scale and so on)
Also I read that installed Helvetica font causes this problem, but I use win 7 and there isn't installed Helvetica font on my computer.
I installed Chrome Canary; there is still problem on webpages.
So, has anybody got an idea to solve this problem.
Related
I have included some fonts in .woff format locally and everything works fine in Firefox and Edge. Only in Chrome, serif fonts are not displayed and the default font is output.
After a few tries, I found that the problem can be solved by disabling "hardware acceleration" in Chrome settings.
After disabling hardware acceleration, the serif font is displayed in Chrome without any problems.
Does anyone have any ideas what causes this issue? In my eyes, it is not due to the code or configurations but is only due to Chrome, because Chrome settings fix the problem. But now it is difficult to explain to potential visitors that it is not a website or code problem.
Any experience or ideas here?
I'm glad to have found the cause finally after lots of research, but unfortunately it's not a real solution. I want to make sure that locally embedded fonts in woff format always work without problems on all browsers.
For all of my chromium based browsers, I'm getting a very bad font within Oryx for ErgoDox. If you're not familiar with the tool, you can see my keyboard layout here.
Update: I'm seeing in "Rendered Fonts" a strange font I don't recognize. Now I'm trying to work out how this is even happening, and why it's all my chromium browsers. See bottom photo below.
Update 2: The current theory is that my system is using the first "sans-serif" font it finds because of a syntax error in ErgoDox's CSS for the font-family; "Lato" should be enclosed in single quotes ' and it is not. This is causing my system to fall back to the first sans-serif font it finds, which is normally something more useful like "Arial", but is pix PixelFJVerdana12pt in my case. I've installed both "Lato" and "LatoLatin" and it is still rendering this awful font.
Update 3: Uninstalling "pix PixelFJVerdana12pt" fixed the issue ?? Now I'm looking into that font to figure out what the heck that even is? Now it renders Lato from the web? I'm putting an updated screenshot at the bottom with it fixed.
Here's what I've discovered and tried:
The site uses "Lato,sans-serif;" for all its fonts - loaded from woff2/woff files hosted on their site.
This problem exists for all of my chromium browsers: Chrome, Brave, Vivaldi, Edge.
The site loads just fine in chromium (Chrome) for a friend of mine.
The site loads just fine for me on my mobile phone.
Extensive searching online yields no reports of anyone else having this issue.
The site displays fine in Firefox.
I've installed Lato to my machine directly from Google Fonts.
I've downloaded the woff2/woff files from ErgoDox and opened them using a woff viewer online; they display correctly there.
Reloading the site with cache disabled does not work.
There are no console, or network errors (in developer tools).
The only extensions I have installed in this instance of chromium are: 1Password, Adobe Acrobat and Application Launcher for Drive (Google).
I run Windows Defender and Malwarebytes Enterprise.
I highly suspect this issue is local to me, and not a more global issue.
Anyone else with this issue? Any suggestions?
Problem demonstration:
Weird rendered font:
After uninstalling "pix PixelFJVerdana12pt":
The solution to the problem was to uninstall the "pix PixelFJVerdana12pt" font. I have no idea what is wrong with it, but it's now working as expected.
Those of you who get your kicks out of IT troubleshooting and mysteries, this is a good one for you to try to figure out! I'd still love to understand why this was happening - so strange.
I think I've figured it out and fixed it on my system - the font pix PixelFJVerdana12pt/PixelFJVerdana12pt by Flashjunior.ch has a TTF UniqueID of 0, which must cause Windows's font handling to treat it differently. I changed this to the font's name in FontForge, and replaced it on my system - after a restart of Chrome, the fonts in Oryx and gameatlas.com seem to be how they were intended to look.
On Chrome (v. 32.0.1700.107) OSX, changing tabs, sometimes happen that the browser doesn't show me properly the font face. It shows me the default one (Times New Roman).
If I go on rollover on those texts the font come back right.
is it a chrome bug?
I import the font face with sass and compass in this way:
+font-face("MavenPro200", font-files( "MavenPro/Light/mavenprolight-200-webfont.woff", "MavenPro/Light/mavenprolight-200-webfont.ttf", "MavenPro/Light/mavenprolight-200-webfont.svg", "MavenPro/Light/mavenprolight-200-webfont.eot"))
+font-face("MavenProMedium", font-files( "MavenPro/Medium/maven_pro_medium-webfont.woff", "MavenPro/Medium/maven_pro_medium-webfont.ttf", "MavenPro/Medium/maven_pro_medium-webfont.svg", "MavenPro/Medium/maven_pro_medium-webfont.eot"))
There is something wrong?
I have experienced this too, definitely a Chrome issue. It is a logged bug which is reportedly fixed in the beta version: https://code.google.com/p/chromium/issues/detail?id=336170
OS: Win 7 64bit
Browser: FF 24.0
If I go to http://www.google.com/fonts it looks awful:
And when I load one for my site locally it looks equally as bad but here is my configuration that I generated from fontsquirrel below:
#font-face {
font-family: 'SecretSans';
src: url('<%=domain_url%>/fonts/secretsansextralight-webfont.eot');
src: url('<%=domain_url%>/fonts/secretsansextralight-webfont.eot?#iefix') format('embedded-opentype'),
url('<%=domain_url%>/fonts/secretsansextralight-webfont.svg#secretsansttextralight') format('svg'),
url('<%=domain_url%>/fonts/secretsansextralight-webfont.woff') format('woff'),
url('<%=domain_url%>/fonts/secretsansextralight-webfont.ttf') format('truetype');
font-weight: 400;
font-style: normal;
}
Because it looks just as bad on the site above and my own site I presume it's an issue with Firefox and/or Windows.
Is there a fix/configuration that will work for all users hitting my site that doesn't require them changing any settings within Firefox or Windows as that's obviously unrealistic.
EDIT1: I just went to Control Panel > Fonts > Adjust ClearType text and now it renders properly in Firefox... I can't ask users to do this though so I'm hoping there is another way
I know this thread is from the stoneage, but unfortunately the problem is still current. And if you google for the choppy fonts problem, it's in the top 10; so I want to add my 10 Cents of experience with it!
Ok: If you search Google for problem with fonts under Vista/Win 7/Win 8, you find two major groups of problems that are both related to ClearType in many cases. Not all! But many.
Group 1: Blurry Windows fonts
If we talk of "Windows fonts" we are talking of the user interface (menus and such), and the "workspace" of office apps like Word or Excel.
This problem hits almost all people that do not have a 16:9 widescreen monitor that is HD capable, esp. classic office-type monitors of 19" and 1280x1024 resolution. The keyword is "Low-DPI" here.
For those who don't know: ClearType does a HORRIBLE job on these Low-DPI monitors and renders the whole interface in such a blurry way that trying to work with it causes massive eye strain and headache. Really folks, it gives you eye cancer!
(and no, you can not recreate that prob' on a Full-HD monitor!)
The only way out is to disable ClearType. This helped almost everybody of group 1 - including me.
Group 2: Choppy font rendering in Firefox and Chrome (rarely MSIE)
In many, many cases - like in this thread - ClearType was disabled. And when re-enabled, the browsers do render fonts just fine. True for me, too!
Unfortunately... when I re-enable ClearType, I'm back in group 1!!!
So: EITHER I have ClearType disabled and can work with a sharp and clear Windows for hours without fatigue of my eyes - but then I have to live with choppy webfonts in FF and Chrome.
OR I re-enable ClearType to see the nice and nifty fonts the designers have chosen for their oh-so-stylish websites - and live with the headache Windows gives me due to the blurry fonts! :-(
Obviously, I'm going the first way.
And if I stumble about a website where fonts look like broken, I simply toggle the usage of webfonts with just one mouse click - there's a great FF-AddOn for that.
Oh, I forgot: Why seems MSIE to render the fonts nicely?
Well, IE (at least 10 and 11 to my knowledge) always uses ClearType to render a page - no matter if disabled in the system settings or not.
Of course, it then also shows the blurry fonts problem - and makes me remember why I have ClearType disabled. And will let it so!
Final thoughts:
Programmers believe webfonts to be the final solution to all of their design-needs, thinking, they have everything under control by testing their stuff on a couple of default systems. In fact, webfonts just made a well-known problem freak out of any control - because there is no such thing like a default user!
Think about it.
I am pretty sure it is just how the browser renders it. Especially with #font-face stuff (I am assuming you used http://www.fontsquirrel.com/ or a similar site to generate it). You can use a little bit of text shadow to make it a little bit crisper, but from what you have shown, I think you might be better off trying to find another very similar font that will render better.
This was obviously because you had ClearType switched off. It's the method used to smooth the edges of fonts on computer screens (LCD). It has nothing to do with the method used in the webpage to attach them, this is strictly a font rendering issue. Fonts may appear differently depending on the system, as each has a slightly different method of rendering them - they tend to look best on Apple systems, while Windows seems to have a somehow inferior rendering method. This is entirely up to the system that is running, so the fonts will render differently for various users. Also, professional fonts from big foundries generally render much, much better than free, open fonts, because they're specifically corrected to optimize how they're rendered on screen, especially when they're rendered small (below 20px size), so the roughness of fonts from the Google Fonts set might also in part be due to the fact they're not as carefully crafted as those professional, expensive ones. Nevertheless, regardless of the font quality, text will always look uglier and choppy if font smoothing is switched off (or not supported), so there is nothing you can do. Stopping yourself from using custom webfonts because you're worried about the fraction of users who have font smoothing turned off is will stop you from using them at all.
I'm using google web fonts for a project, and have had no issues so far. I have a text shadow applied to some areas, and was pretty happy with the result in Chrome. I switched over to FF and the text was dizzyingly blurry. This applied to all text, shadow or not.
Is this a google web font issue, or something else?
Here's a screenshot of chrome
...and FF
I'm also having many issues with this at the moment...
You can try adding font-weight:normal; or font-weight:100; to your CSS, but I have found this work only sometimes.
My fonts all work correctly on FF (even IE) on PC, but using FF on MacOSX (Snow Leopard) they give that bold/blurry effect :(
Try toggling the hardware acceleration in options/preferences > advanced.
Read somewhere that rendering of fonts changed with increasing usage of hardware acceleration.
Also you can try tweaking at OS level. Go to system preferences > Appearances > Font-smoothing and tweak options there. Many people find blurry font issues because of mac's font-smoothing technique.