Thread:2Actimv/@comment-188432-20150116185246/@comment-188432-20150116200848

Okay, so I've verified that you can now see this font change in all supported browsers, except for IE. I've been able to check w:c:bejeweled where, even in IE, I'm still getting the same custom fonts. Your MediaWiki:Common.css call is based rather precisely on Bejeweled's. The only difference is the server being used. We are currently experiencing some service issues with our image servers, and you're using an address that's a temporary workaround. If I haven't gotten back to you in two weeks — the amount of time likely for a fix to actually go live — please add a note to this thread, and ask me for a status update. IE is the trickiest of the tricky when it comes to syntax and I'd put all the money I have on it just not liking this particular URL. (It probably sees it as cross-domain or something, which is a no-no with font importation.)

Anyway, we're basically there with this font, save this tiny niggle that affects only a fraction of users. Still, since this is going to be a major feature of the wikia immediately, I think you do have to build in a font stack so that IE people can get a sorta close match. The format of a font stack is: .CaptureItNow { font-family:"CaptureIt","Font 2", "Font3",sans-serif } where Font 2 and Font3 are close matches that people are likely to have on their machines. You can find out probability matches for fonts by going to any number of places on the web by searching for "font stack builder", but to save you some time, this one gives you the probabilities for sans-serif fonts right at the top: http://www.cssfontstack.com/.

One last thing: when you write a font stack, you're going to want to put the least likely things before the more common things, so that more of your users have the experience you want. If you put the common windows fonts at the font, that's what most people will see, and you probably don't want that. So basic order would be: .CaptureItNow { font-family:"CaptureIt" (always put first, because this is the one you actually want people to see), "Mac Font at 95%+", "Windows Font at 95%+", sans-serif }

Of course, you can put more than three fonts, if you want. For instance, you may want to put a font that only 75% of Windows users have immediately, before the 95% Windows font, but you don't have to.

And after we get this little image server problem fixed, you really won't need a font-stack at all, though it's not a horrible idea to go ahead and at least add "sans-serif" in case something weird happens that we can't now foresee.