When I use Google Webfonts, they load fine on every browser I care about, EXCEPT Chrome/iOS. This seems odd, as it works fine on Chrome for Mac and Safari for iOS, so I don't think it's an iOS problem or a Google Chrome problem. It seems to be specific to Chrome/iOS.
Any ideas, or ideas on HOW to troubleshoot this, would be great!
Thanks!
EDIT
I am using Google Web Fonts hosted on Google, with the following:
<link href="http://fonts.googleapis.com/css?family=Leckerli+One" rel="stylesheet" type="text/css" />
In my font (SASS), I am using the following:
h1
font-family: "Leckerli One", cursive
I'm seeing the same issue. Hosting the font files on my own server and rewriting the #font-face rules to match solved the issue for me, both with my local dev server and in prod.
I don't know the cause; my best guess would be some same-origin issue that's enforced differently in UIWebViews (iOS Chrome being a UIWebView due to App Store rules).
You can use the Google Fonts API Loader which will detect the user's browser and send back appropriately formatted CSS.
Sample code is available in the first response on this Stack Overflow question.
This will allow both Safari and Chrome (and other UIWebView-based browsers) to display the font correctly.
Note: if you want to store the fonts locally, as #Dave suggested, this CSS should work.
IOS devices use TTF formats only (or OTF if they follow the developer guidelines below). That font is being served as WOFF, EOT and OTF (assumably not following the guidelines) . There are some services that will give you other versions. Try specifying the font using #font-face and see if that fixes the issue! Fontsquirrel has an #font-face generator to do the heavy lifting.
In regards to the follow up question. There are some developer documentation from Apple on their implementation of TrueType Fonts. It can be found here. Essentially, TTF formats store the font as sfnt resources. The only other font format that can do this is OpenType's offset table sfnt wrapper. Because IOS reads fonts using sfnt wrappers, you will run into issues with fonts that are not stored in this way. (Sorry for all the jargonny talk).
In the CSS you may use
!important
Example:
#font-face {
font-family: 'Monda' !important;
font-style: normal !important;
font-weight: 400 !important;
src: local('Monda Regular'), local('Monda-Regular'), url(http://themes.googleusercontent.com/static/fonts/monda/v1/sk05J8GA1NvUxDnk43EgAQ.woff) format('woff') !important;
}
In case anyone else still sees this issue - a font not loading in Chrome on iOS 9 or older - double check that the font is imported as a css file, and not as a js file. Fonts.com will give you the option to import fonts as js, which won't get picked up on Chrome / iOS 9 or below. Changing my import to css fixed this for me.
For me works add in php page:
<style type="text/css">
#import url('https://fonts.googleapis.com/css?family=Trocchi');
#import url('https://fonts.googleapis.com/css?family=Montserrat:100,100i,200,200i,300,300i,400,400i,500,500i,600,600i,700,700i,800,800i,900,900i');
</style>
I've got similar problem with UIWebView lately. I made additional changes to both iOS app and web source, nothing helped.
Finally fixed it by simply changing Google Font's link to https.
Related
I have some icon fonts in an #font-face declaration in my styles that do not show in Safari iOS until the user chooses to refresh the page. The project is built on ember, so refreshes will never happen if the user does explicitly do it themselves. I know the icon fonts are loading because they show on refresh, but Safari just disregards them until I do. I have searched for days for a solution but can't find anything that works.
Has anyone run into this issue with a solve?
=== EDIT ====
here is my #font-face declaration for reference:
#font-face {
font-family: 'designcenter';
src:url('../fonts/designcenter.eot?-s17jdf');
src:url('../fonts/designcenter.eot?#iefix-s17jdf') format('embedded-opentype'),
url('../fonts/designcenter.woff?-s17jdf') format('woff'),
url('../fonts/designcenter.ttf?-s17jdf') format('truetype'),
url('../fonts/designcenter.svg?-s17jdf#designcenter') format('svg');
}
So after some experimenting and changing, I found that if I took the value of designcenter out of quotes, either single or otherwise across the project, it seems to consistently work.
So just as a recap, iOS8 Safari cannot handle quotes for font face values. I hope this helps out anyone in the future.
This Magento 1.4.1.1 website needs this markup:
<meta http-equiv="X-UA-Compatible" content="IE-EmulateIE8"></meta>
to work under IE9 to IE11 (prototype compatibility reasons).
With IE9 all is fine (I can't test with IE10).
But with IE11, the google font Playball used mainly on the header is not shown correctly. IE11 shows an other unknown (for me) font.
This issue is directly connected with the specific markup because if I deactivate it all becomes fine. I red on another post:
Google is only offering the font in .woff format. IE8 doesn't support
.woff, so the browser (acting like IE8) ignores it.
For the moment I use the normal Google API to be able to use this font, including:
<link href='http://fonts.googleapis.com/css?family=Playball' rel='stylesheet' type='text/css'/>
My question is:
maintening the markup, is there a workaround, or another way to include the font on the website, to be able to show correctly the google fonts with IE11 (and other browsers, of course) ?
I found an efficient workaround:
If your server is apache, you can replace this directive in the by 2 lines on the .htaccess file at the root of your website:
BrowserMatch MSIE best-standards-support
Header set X-UA-Compatible IE=8 env=best-standards-support
With this I have no more problems with Google fonts under IE10 or IE11 even emulating IE8.
I use Bootstrap 3.0.3 glyphicons. All is ok on desktop browsers and on Android devices. My problem is about Apple devices (tested on iPhone and iPad running iOS7).
The glyphicons look like emoticons. I've found some issues but not answering my problem.
Here is the link to view the screenshot : http://www.fredericblancheton.fr/imgdisallow/image.png
Thank you for your help.
I had a similar problem, but only when another font was included via font-face inside the stylesheet. It seems that mobile safari or safari in general has a very short timeout for loading fonts which are included via font-face syntax.
I had to remove the font from the main stylesheet and add the font-face syntax directly in the sites header using <style></style> syntax. Weird.
Another approach is illustrated over at filamentgroup, which are using the Data-URI syntax for the font and loading these asynchronously via javascript. This should also trick the browser to wait longer.
-> http://www.filamentgroup.com/lab/font-loading.html
We've seen the same problem in our app - it's totally bizarre. It happens when the user has installed an old Emoji app ("Emoji Free!", which I can no longer find in the app store).
The only solution was to get the user to uninstall the app.
I encountered same issue and resolved it by removing woff2 font file from #font-face. It seems iOS doesn't support woff2.
[Updated 2016-03-02]
Fix above turns out just matter of luck (timing?).
#rofflox 's answer which seems to be more promising and it works for me.
I just tried the solutions above and none of them worked for me. It turned out that:
I had updated bootstrap to 3.3.6 css
I didn't update the font files that came with it
Getting the latest version of the font files fixed my issue with the unwanted emojis.
I started getting this error today using Pulsar for Salesforce, I turned out that my FE DEV had included references to Fonts and forgotten to update the static resources with the new fonts! In case that helps someone.
I am using some Google web fonts for my website, Arabic fonts, from here http://www.google.com/fonts/earlyaccess
I import these fonts in my css
#import url(http://fonts.googleapis.com/earlyaccess/droidarabickufi.css);
#import url(http://fonts.googleapis.com/earlyaccess/droidarabicnaskh.css);
The fonts work just fine everywhere but not on ipad. I tried to google the issue and I came up with this Stack question that suggests SVG. Any clues on how to get SVG for Google web fonts? Thanks
I solved it, Google fonts don't have SVG format in their defaults of these fonts, I had to download them and get the SVG format, re-include my fonts and it worked well so far on iPad Peek, with test them and get a final feedback
I haven't read all of the terms of use, but they give you access to download the font. I believe you can then take that font to Font Squirrel and it will generate you the font types you need (and CSS #font-face styles) so you can self-host the font yourself.
Simple questions.
Can you change the color of sIFR after the flash has been applied?
I have a bit of a Google, but can't seem to find anything. Only people not being able to set the color initially.
Thanks
I don't know about sIFR, but on a side note, I'd heavily recommend CSS 3 embedded fonts over the aesthetically displeasing sIFR, which is inaccessible, slow and can't be copied along with selected text.
As Delan mentioned, I would suggest not using sIFR anymore. With the browsers currently in use, you have pretty decent CSS support. Convert your TTF to EOT for older versions of Internet Explorer, using this tool for example: http://www.kirsle.net/wizards/ttf2eot.cgi
Then use this CSS. In this case my font is called Techno:
#font-face
{
font-family: Techno;
src: url("/Techno.eot") /* EOT file for IE */
}
#font-face
{
font-family: Techno;
src: url("/Techno.ttf") /* TTF file for CSS3 browsers */
}
This covers recent Safari (3.1+ afaik), Firefox (3.5+) and Opera versions. Mobile Safari doesn't do this, but wait, it doesn't do Flash either :)
Well, after contacting the font companies, it seems I can use cufon (with the purchase if another license, which is the same as sIFR anway). S0. I have decided to go with cufon...