Databases
StackOverflow2013
Postsdbo
POGoogle Web Fonts not showing properly on IE9
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGoogle Web Fonts not showing properly on IE9
    text
    copied!<p>I am using Google Web Fonts. All browsers are rendering the font properly except IE9. (I haven't tested on earlier versions of IE).</p> <p>Here is the difference: <a href="http://mojoimage.com/free-image-hosting-view-11.php?id=3317Capture.PNG" rel="noreferrer"><strong>IE 9</strong></a> vs. <a href="http://mojoimage.com/free-image-hosting-view-11.php?id=3336Capture2.PNG" rel="noreferrer"><strong>Google Chrome</strong></a></p> <p><strong>HTML:</strong></p> <pre><code>&lt;head&gt; &lt;link href='http://fonts.googleapis.com/css?family=Yeseva+One' rel='stylesheet' type='text/css'&gt; &lt;meta charset="utf-8"&gt; &lt;meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"&gt; &lt;title&gt;&lt;/title&gt; &lt;meta name="description" content=""&gt; &lt;meta name="viewport" content="width=device-width"&gt; &lt;!-- Place favicon.ico and apple-touch-icon.png in the root directory --&gt; &lt;link rel="stylesheet" href="css/normalize.css"&gt; &lt;link rel="stylesheet" href="css/main.css"&gt; &lt;script src="js/vendor/modernizr-2.6.2.min.js"&gt;&lt;/script&gt; &lt;/head&gt; </code></pre> <p><strong>Google Fonts file contents:</strong></p> <pre><code>@font-face { font-family: 'Yeseva One'; font-style: normal; font-weight: 400; src: local('Yeseva One'), local('YesevaOne'), url(http://themes.googleusercontent.com/static/fonts/yesevaone/v6/wVgDKaRrT3DN9VGcOY4orxsxEYwM7FgeyaSgU71cLG0.woff) format('woff'); } </code></pre> <p><strong>CSS:</strong></p> <pre><code>.sf-menu li { float:left; position:relative; text-align:center; font-family:'Yeseva One',cursive; font-size:17px; line-height: 64px; border-bottom:1px solid #4A4A4A; } </code></pre> <p>What should I do?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload