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
Related
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.
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.
I've been struggling for hours now, to figure out why font-awesome isn't functioning properly. I used the Font Awesome Wordpress plug-in. It works for the majority of the browsers, however Firefox is showing only a few characters.
It's the magenta menu on this website: http://www.babystuf.nl. (the blocks in the left sidebar) I tried everything (updates to Font awesome 4.X without the plugin, added .htacess in the /font folder, changed the .. /fonts/ path to a static path). Without succes.
Weirdest thing is, that we run a copy of that same website (http://www.baby-wereld.nl) and it's working fine there! Different server, same WP version, however with less plugins than babystuf.nl.
Who has an idea on how to fix this?
Thanks! M
UPDATE: It turned out that we used the All In One Event Wordpress plug-in, that uses Font Awesome as well… And that's a older version than 3.2.1. Only Firefox loaded that font set…
I had this problem. I thought I had tried EVERYTHING (htaccess, changing file paths, playing with permission, etc) but it turned out I had previously tried to use a Font Awesome plugin in my wordpress installation and Firefox was picking up this older version of FontAwesome. Disabling the plugin let the browser look for the files I had uploaded myself and the problem is now solved!
I am working on a project where client wants to use MotivaSans-Bold.
However on windows browsers it displaces text on twitter bootstrap enabled buttons but looks good on Mac browsers. But if I try to change padding it disrupts Mac browsers.
What can be the problem? Is there any problem associated with webfonts?
EDIT
#font-face {font-family: 'MotivaSans-Bold';src: url('webfonts/279BB3_D_0.eot');src: url('webfonts/279BB3_D_0.eot?#iefix') format('embedded-opentype'),url('webfonts/279BB3_D_0.woff') format('woff'),url('webfonts/279BB3_D_0.ttf') format('truetype');}
The problem is most likely that the spacing on the webfont is going to vary from browser to browser. What's probably going on is that on Chrome on the Mac the font and button look good, but then Firefox on Windows 7 the fonts renders slightly larger and throws off your button.
You should be able to address this with padding/margin via CSS as long as you don't try to set any fixed widths.
If you post a link to the page it'll be easier to suggest a more specific answer, but if the webfonts look relatively similar both Mac and Pc than there's nothing 'wrong' as far as the font goes and it's really a CSS issue.
I got a really strange problem, and after so much tries and research I can't get out of it.
I have a website, but SOME (just 5% of visitors) people with the SAME version of chrome, see the text flowing out of divs and text overlapping. It's very strange because I tested the website on all chrome browsers using browser testers, without any problem. And in internet explorer or firefox this problem never happens...
A page is located here
And here are some screenshots of what SOME people see (maybe you won't see this in chrome)
click here
Maybe it is because of the font face I am using? Or maybe some bad coded CSS?
Please help me out of this!
Thanks a lot!
I see you use .svg font. Recently I was hunting some Chrome font rendering bugs and saw this:
http://code.google.com/p/chromium/issues/detail?id=95102
This seem very similar to issues you are having. You could try to serve some other font type to Chrome and if this would fix that.
If you don't want or can't serve some other font type to Chrome, the only thing you can do is wait until Chrome version 24 is out to all users which should be soon (I can't find any announcement)
I tested it in
Chrome 23.0.1271.97 m
Chrome 26.0.1371.0 canary
Chromium 25.0.1334.0 (169326)
# Windows 7 x64 and your page seems fine for me.