Remember those custom fonts that we had on headers and body text? The “HaloWaypoint” stencil font and that nice “KonsensRegular” font for posts? Whatever happened to those? All we have now is crappy Times New Roman and Arial.
Well, as it turns out, moving the forums broke the URLs in some of its stylesheets. Here’s a picture of me examining the broken code in a debugger:
There’s your problem!
I went to the main Waypoint server, where the fonts still work, and used the CSS there to reconstruct the URLs. I used the debugger to inject the fixed URLs into the forum index…
Gentlemen, BEHOLD!
I couldn’t find the code for the KonsensRegular body font, but the fix for that should be the same.
EDIT: TL;DR: Fonts need to be changed from relative URL fonts/… to absolute URL /Content/fonts/…
So basically, when the forums moved, they forgot to move the fonts with them?
Is that something exclusive to Firefox, because the fonts are working perfect for me on Chrome right now, including the custom HaloWaypoint one.
> Is that something exclusive to Firefox, because the fonts are working perfect for me on Chrome right now, including the custom HaloWaypoint one.
It’s working for me too.
> So basically, when the forums moved, they forgot to move the fonts with them?
I think they moved the fonts on the forums and the main site, but only updated the main site’s copy of the files that use the fonts.
> Is that something exclusive to Firefox, because the fonts are working perfect for me on Chrome right now, including the custom HaloWaypoint one.
The only explanation I can think of would be that the site is sending Firefox or Chrome a different set of CSS code. Doing that would be bizarre, problematic (because user-agent detection is all a server has, and that’s unreliable), and wrong (because the only reason to do it would be if the CSS code is broken in which case you should fix the CSS!), but it’s the only explanation I can think of. :\
Uh, do you know how to use Chrome’s Element Inspector? Could you have a look at the top of theme.css, and copy and paste any of the URLs that have “konsenssten” in them?
> > So basically, when the forums moved, they forgot to move the fonts with them?
>
> I think they moved the fonts on the forums and the main site, but only updated the main site’s copy of the files that use the fonts.
>
>
>
> > Is that something exclusive to Firefox, because the fonts are working perfect for me on Chrome right now, including the custom HaloWaypoint one.
>
> The only explanation I can think of would be that the site is sending Firefox or Chrome a different set of CSS code. Doing that would be bizarre, problematic (because user-agent detection is all a server has, and that’s unreliable), and wrong (because the only reason to do it would be if the CSS code is broken in which case you should fix the CSS!), but it’s the only explanation I can think of. :
>
> Uh, do you know how to use Chrome’s Element Inspector? Could you have a look at the top of theme.css, and copy and paste any of the URLs that have “konsenssten” in them?
F12 brings it up in Chrome.
It’s actually happening because the fonts are being served from a different origin.
Both Firefox and Internet Explorer apply the same origin policy to font files (Chrome and Safari do not). This is why they aren’t loading. The CSS is correct.
> > So basically, when the forums moved, they forgot to move the fonts with them?
>
> I think they moved the fonts on the forums and the main site, but only updated the main site’s copy of the files that use the fonts.
>
>
>
> > Is that something exclusive to Firefox, because the fonts are working perfect for me on Chrome right now, including the custom HaloWaypoint one.
>
> The only explanation I can think of would be that the site is sending Firefox or Chrome a different set of CSS code. Doing that would be bizarre, problematic (because user-agent detection is all a server has, and that’s unreliable), and wrong (because the only reason to do it would be if the CSS code is broken in which case you should fix the CSS!), but it’s the only explanation I can think of. :
>
> Uh, do you know how to use Chrome’s Element Inspector? Could you have a look at the top of theme.css, and copy and paste any of the URLs that have “konsenssten” in them?
You would have to run me through it.
edit again:
ok, after a little more exploring of the chrome bug thingy, i found my way to theme.css and here is the screencap
> edit again:
> ok, after a little more exploring of the chrome bug thingy, i found my way to theme.css and here is the screencap
Thank ya kindly, bro.
That is very strange… You’re receiving the same broken URLs in Chrome that I’m receiving in Firefox, yet Chrome still manages to find and use the font files. It shouldn’t even be able to find those files, because the one piece of information it has to go on is wrong. Bizarre.
Fixing the URLs should fix it for Firefox, but I almost suspect it might break things for Chrome. For some reason, it’s either finding a way to make the bad URLs work, or it’s getting different URLs from some other source that I can’t locate (don’t have Chrome with me at the moment).
The issue has nothing to do with the URL to the fonts being incorrect. It’s because the same origin policy in Firefox and Internet Explorer is also applied to font files, and since the font files are being served from a different domain, the browser won’t render them. The CSS being delivered to all browsers is exactly the same.
> The issue has nothing to do with the URL to the fonts being incorrect. It’s because the same origin policy in Firefox and Internet Explorer is also applied to font files, and since the font files are being served from a different domain, the browser won’t render them. The CSS being delivered to all browsers is exactly the same.
Wait, so you’re saying that the URLs are relative to the location of the CSS file (on msecnd.net), not the current page?
Good catch. That makes sense. What I don’t understand, then, is why there’s a separate and working copy of the font files on the forums.halo.xbox.com domain. And isn’t Chrome violating the spec by not applying same-origin limitations?
mhm, i opened up firebug in firefox (the addon being used to view and edit source), changed it from source edit to live edit then added a forward dash into the URLS infront of font and it works.
hm …
edit:
nevermind, just tested it again and now i have to put a forward dash infront of content
> Is that something exclusive to Firefox, because the fonts are working perfect for me on Chrome right now, including the custom HaloWaypoint one.
Weird, I have yet to see fonts on Waypoint. Im also using Safari if that helps at all…
> > Is that something exclusive to Firefox, because the fonts are working perfect for me on Chrome right now, including the custom HaloWaypoint one.
>
> Weird, I have yet to see fonts on Waypoint. Im also using Safari if that helps at all…
Interesting… Chrome and Safari share a lot of the same code under-the-hood, but Waypoint’s fonts only show up in Chrome.
Supports my theory: Chrome is reading the wrong URLs the wrong way, which (ironically) leads to the desired result. If the 343i devs change things to use the right font URLs, then all browsers should read them the right way, fixing the bug.
