font URL is different from other libraries
See original GitHub issuein the summernote.css
, the @font-face
declaration using source url like font/summernote.eot
but not ../fonts/summernote.eot
, please check that in Bootstrap, they use src: url('../fonts/glyphicons-halflings-regular.eot');
.
For a better compatibility, I suggest you must change the @font-face
declaration to a common format.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
What sites provide public web font libraries to link to?
What sites provide public web font libraries to link to? · css · fonts · font-face · webfonts.
Read more >Web fonts - Learn web development - MDN Web Docs - Mozilla
Fonts are created by font foundries and are stored in different file formats. There are generally three types of sites where you can...
Read more >Best practices for fonts - web.dev
This article discusses performance best practices for fonts. There are a variety of ways in which web fonts impact performance:.
Read more >Create and manage font collections and libraries in Font Book ...
Create a collection · In the Font Book app on your Mac, do one of the following: Choose File > New Collection, then...
Read more >Using web fonts – Fonts Knowledge - Google Fonts
Reference the font files. Link copied! ... In our CSS file we'll first need to create a family reference for the font files...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
My question is not about why you use custom font except the font-awesome, it’s about the
@font-face
reference URL difference: origin:expected:
Please focus on this point of view, thanks.
this issue has been resolved.
please use a latest version