We have recently developed a website with a strong reliance on Font Awesome as part of it's design. We're using the standard implementation with before:content and their supplied CSS. For some reason Font Awesome isn't displaying in IE8. I've spent quite a few hours troubleshooting and trying various fixes, with no luck. I have:
Here is the website: http://www.tetakere.org.nz - the Hotlinks box is a good example of Font Awesome Has anyone got any ideas on other approaches to getting this website to display Font Awesome? |
|||
add a comment
|
After some painful troubleshooting I finally worked it out. The solution was to move the loading of HTML5Shiv from the
|
||||
I tried everything from modifying my apache config, and .htaccess files with no luck. In the IE development tools I stumbled upon "Document Mode" and the default was IE7. So after some research I found this meta tag:
Now IE 10, and 9 format my website correctly and display all Font Awesome icons correctly. If you still want IE 8 compat then you could start with this:
Hope that helps... |
|||
I know this is an older question, but I had lots of trouble with this issue and none of these answers helped except the last one. Changed the head... What worked for me was:
This also worked (last answer I referred to):
Also, I read (Force IE compatibility mode off in IE using tags) that you should put that meta tag above all other meta tags and before any conditional IE statements; otherwise the meta tag will be invalidated. |
|||
I did not need html5shiv to get FontAwesome to work in IE8. This answer (re-creating the .eot file and replacing the old one) solved my problem. |
|||
but finally works when added
files happy coding |
aaa
Why does this fontface render in IE8:
And this does not:
I really can't figure it out. All other browsers work fine, obviously. |
||||
Try creating a new
If this new file doesn't work, then it might be a problem with the font itself. Sometimes IE6-8 has a fit if the Fontname and Family Name are not the same within the actual font file. To fix it:
Every issue I've had with font-face - if the CSS was correct - worked with one of the above two solutions, so good luck 🙂 Maybe even try saving the font without any changes in FontForge and converting that online before you fiddle with the name properties. |
|||||||||||||||||||||
|
but finally works when added
files happy coding... by sivakumar |
|||
Under IIS (MVC environment) I had to add the following rule to my Web.config:
|
html5-shiv
AFTER FontAwesome to solve this issue. See stackoverflow.com/questions/9809351/…. – leesei Apr 23 '13 at 17:38