Closed christophsax closed 9 months ago
Ouch! This is what I see on Firefox:
But on Chrome I can see the issue too.
Must be a CORS thing, exploring now.
Related #15
Could it be a CORS isse this time? Or did the rules change in cynkraweb
Font rules
Today is the first time I see this. On all browsers. I am not aware we changed stuff in cynkraweb but then I may overlook something.
I don't see changes in the relevant cynkraweb scss file. I don't see any error in the web developer console.
I managed to see a CORS error:
blog.cynkra.com/:1
Access to font at 'https://cynkra.com/assets/css/fonts/1449009/b3ca2df2-7bee-4fc0-84cb-b029b99c3b61.woff2' from origin 'https://blog.cynkra.com' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header has a value 'https://www.cynkra.com' that is not equal to the supplied origin.
@pat-s is this an easy CORS switch? sorry to bother you once again about fonts :sweat_smile:
CORS is fixed, but it seems the font still cannot be loaded from the source.
Thank you! Do you have any idea what might be wrong? I'll explore more next Monday...
I have the issue for the preview at GitHub pages, but https://blog.cynkra.com/ looks ok to me now?! or maybe only the headers. I'm really confused now.
I wonder whether this could be linked to the font files that had the "wrong" names at one point @christophsax @pat-s?
https://blog.cynkra.com/ is still not showing fonts. You can check this in a private window.
There are no devtools errors in the browser about something being blocked or not accessible, so the issue is likely in the source/css somewhere.
@DivadNojnarg found the typo I had made :woman_facepalming: