You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The example of the effect of CORS in section 4.9 ‘Font fetching requirements’ says that the font specified with src: url(https://example.com/fonts/simple.woff) fails to load, due to having a different scheme than the document. However, the scheme, ‘https’, is actually the same.
Probably the example was meant to have ‘http’ instead of ‘https’: src: url(http://example.com/fonts/simple.woff)
The text was updated successfully, but these errors were encountered:
Hello everyone,
I noticed the same thing regarding the scheme.
I didn't think a reference of the commit to my fork (542ad1d) would already appear, here.
Would it be okay to open a pull request?
The example of the effect of CORS in section 4.9 ‘Font fetching requirements’ says that the font specified with
src: url(https://example.com/fonts/simple.woff)
fails to load, due to having a different scheme than the document. However, the scheme, ‘https’, is actually the same.Probably the example was meant to have ‘http’ instead of ‘https’:
src: url(http://example.com/fonts/simple.woff)
The text was updated successfully, but these errors were encountered: