-
Notifications
You must be signed in to change notification settings - Fork 32
Page title fonts look wrong on Chromium 49.0.2623.108 running on Ubuntu 15.10 (64-bit) #20
Comments
@snim2, when you look at the network tab in developer tools, do you see any resources failing to load? |
I think @hawkz may have answered this elsewhere, but this was the resource: |
@hawkz says "The font will work on 127.0.0.1 and the live domain. It's a licensing thing. I'll try to add 0.0.0.0". @snim2, can you confirm that http://2016.pyconuk.org/home/ looks OK? |
That makes no difference to me, I get an error called |
Paging @meshy as another Linux user. |
Ha! Well, this is rather embarrassing. If I turn my ad blocker off the error in the dev. tools pane disappears, but the fonts still overlap. I think perhaps I am overriding all the fonts in my Chromium settings. In FireFox it looks a little better, and I think the two browsers use the same rendering engine: |
Firefox and Chrome use different rendering engines. |
OK! So we should have some kind of fallback in case fonts can't be loaded, but I don't think this is a blocker for launching today. |
Nope, my "Tickets" and "Contact" are nicely separated out. Even if I resize my browser I can't reproduce #40 in Chromium. |
OK -- I'm not clear on what the problem is then. (I'm probably being dense.) Which are the fonts that overlap? |
The font we use at PyConUK isn't free (because the classic ones generally aren't) Typekit hosts it and blocks requests from other domains. I've added 0.0.0.0 to the list of whitelisted domains - might fix your local test now. The list is now: "pyconuk.org, .pyconuk.org, pyconuk.net,.pyconuk.net, localhost, 127.0.0.1, 192.168.2.250, 0.0.0.0" |
can we get a re-test, think this is cleared, I'll add a better fall-back as per #51 to handle this better. (It's the difference in glyph width that's throwing off the spacing) |
Assigning to @snim2 to test. |
@snim2 A bit late, but is this fixed? |
Yes, all looks good to me, thanks! |
Reported by @snim2.
The text was updated successfully, but these errors were encountered: