This likely isn’t a Hype issue, but I’ve been working all week on a Hype document that uses custom fonts with the usual @fontface method like I always do, with no issues. Then today I noticed this message in the Chrome console (local preview)…
I’m on Chrome v 66.0.3359.117 with no extra extensions. I supposed it could have auto updated overnight. I’m not sure what my previous version was. Just odd that yesterday I wasn’t getting this console message.
16 Mbps, which is about what I should be getting but this shows up in the console both in a local preview with the fonts included in the library and online. I can hide the error by checking ‘disable cache’ while in dev tools. The only thing I can think of here is that I was using an earlier version of Chrome that was unknowingly just updated. It’s kind of annoying, but the fonts seem to be loading fine and since I can hide the console error I can live with it. Just a head scratcher that seemingly came out of nowhere, but apparently it’s been known for a while.
I don’t think it is anything to worry about if it only happens from the Hype Preview server.
However I did try investigating and couldn’t reproduce it myself with a test font. Do you mind attaching a zip of your .hype document since it might have to do with your specific fonts? (feel free to email to support@tumult.com if you need it kept confidential).