What happened to our custom webfont?

Mark Simonson
Mark Simonson Posts: 1,734
in Suggestions and Bug Reports
I've noticed this for a couple of days now. Fake-bold Lucida Grande looks horrible.

Comments

  • Dyana Weissman
    Dyana Weissman Posts: 331
    edited January 2018
    That is unfortunate. However, I don't see any Lucida Grande. Let's narrow down what's causing the error. Do you mind posting a few screenshots? What OS/browser are you using?
  • Thierry Blancpain
    Thierry Blancpain Posts: 210
    edited January 2018
    Same here


  • Florian Hardwig
    Florian Hardwig Posts: 269
    Alright Sans used to be served via this file:
    https://cloud.webtype.com/css/6c63ed70-2774-426a-ae79-244b0000b824.css
    Expired?

  • Mark Simonson
    Mark Simonson Posts: 1,734
    edited January 2018
    Here's what I'm seeing:





    This is in Safari 11.0.2 on macOS 10.13.2. The fake bold looks less bad in Chrome, but also seeing Lucida Grande there and in Firefox.
  • Kent Lew
    Kent Lew Posts: 937
    I’m also seeing Lucida Grande (which is the last fallback in the font stack). Seems like the "Alright Sans from Webtype" is not being served right now for some reason. Maybe expired, like Florian suggests.
  • Dyana Weissman
    Dyana Weissman Posts: 331
    Thanks for posting those. That is frustrating. That's interesting that you see it in Chrome, too, which is what I'm using. 

    Either way @James Todd and @Tiffany Wardle have more powers than I do so let's make sure they see this. 
  • Dyana Weissman
    Dyana Weissman Posts: 331
    …I will also check with Webtype.
  • Mark Simonson
    Mark Simonson Posts: 1,734
    Here's Safari, followed by Chrome:



    The main difference seems to be how the fake bold is spaced, but they are both Lucida Grande.
  • Dyana Weissman
    Dyana Weissman Posts: 331
    Thanks. Webtype suggests it may be a cache issue. Do you wanna try clearing that and let me know if it works? 
  • Mark Simonson
    Mark Simonson Posts: 1,734
    That's funny. Without doing anything, it works on my desktop Mac again. My laptop was still affected, but emptying the cache fixed it. Thanks!
  • Mark Simonson
    Mark Simonson Posts: 1,734
    Seems like this needs to be done for each browser to fix them all. I guess something changed on the server end, leaving cached data invalid or something?
  • Thierry Blancpain
    Thierry Blancpain Posts: 210
    A hard reload (CMD + Shift + R) seemed to do the trick for me.
  • Dyana Weissman
    Dyana Weissman Posts: 331
    Must be something on the server. Maybe Vanilla was doing something. Glad to hear the cache clearing worked.
  • Kent Lew
    Kent Lew Posts: 937
    Hmm. Didn’t work for me. Still seeing only Lucida after clearing browser cache.
  • Florian Hardwig
    Florian Hardwig Posts: 269
    Check out the CSS file I linked to above. It should reference the fonts, but apparently it keeps getting truncated after the introductory comment. It was incomplete for me the other day, a hard reload brought the full version, now it is incomplete again.
  • Dyana Weissman
    Dyana Weissman Posts: 331
    I've nudged Webtype again, and they are sending some self-hosted fonts to the Administrators. 
  • Thomas Phinney
    Thomas Phinney Posts: 2,883
    I still get Lucida Sans Unicode, too. Even after clearing cache. (latest Chrome on macOS 10.12.6)
  • James Hultquist-Todd
    James Hultquist-Todd Posts: 417
    I’ve been speaking with Vanilla about this and hope to have it resolved soon.
  • Roel Nieskens
    Roel Nieskens Posts: 188
    The caching data for the fonts has been reset on January 18th, looks like Webtype served a new CSS file from then on. Getting the proper webfonts here now. Anybody still getting Lucida?
  • Kent Lew
    Kent Lew Posts: 937
    I’ve been seeing Alright Sans again now since yesterday morning.
  • Mark Simonson
    Mark Simonson Posts: 1,734
    Seems to be working okay for me the last day or two.
  • Thomas Phinney
    Thomas Phinney Posts: 2,883
    Looks good now.

Categories