i’m not sure why but sinka-mono and eiko fonts can cause a cors error . loading from cdn urls: https://bk.kinopio.club/fonts/shinka-mono/ShinkaMono-Bold.woff2 . maybe related to https://stackoverflow.com/questions/52893199/cors-issue-with-woff2-fonts-behind-cdn-in-chrome
1 Like
I definitely see this from time to time.
seen in Kinopio
1 Like
From MDN: “In many cases, it is caused by a browser plugin (e.g., an ad blocker or privacy protector) blocking the request.”
Looks fine in Safari.
1 Like
oh interesting! I wonder why images and other fonts from that same s3 domain load though for us?
See also: @font-face - CSS | MDN
Web fonts are subject to the same domain restriction (font files must be on the same domain as the page using them), unless HTTP access controls are used to relax this restriction.
this might be a good clue. i’ll try hosting the fonts inside the kinopio repo so they’re served from the same url and not from an s3 bucket
1 Like
beta release includes a fix for this
the new version with a fix for this issue is now shipped