Problems caused by replacing font-awesome with custom font
See original GitHub issueThis issue is for discussion. Most plugins had used pre-included font-awesome icons for their buttons and other UI.
But this was deleted by v0.8.0
by using custom font files.
How could we handle this? Do we should use own icons or font files for each plugin?
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (11 by maintainers)
Top Results From Across the Web
Troubleshooting | Font Awesome Docs
Try using Conflict Detection to spot any problems like this. If your site is loading multiple conflicting versions, then you should solve that...
Read more >FontAwesome & Custom Fonts Not Working - Themeco
I'm again having issues with both FontAwesome and a custom icon ... is stripped from the Wordpress text box and replaced with (a...
Read more >Font Awesome 5 font-family issue - css - Stack Overflow
Using the fontawesome-all.css file: Changing the "Brands" font-family from "Font Awesome 5 Free" to "Font Awesome 5 Brands" fixed the issues I was...
Read more >How To Fix Missing Font Awesome Icons Or Custom Fonts
In some cases, when users migrate sites, the Font Awesome files can still show a path to the old site, and this causes...
Read more >Troubleshooting Font Awesome icons
The main indicator of icon trouble is seeing a blank box instead of the icon itself, but there can be other problems that...
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
@lqez I agree with your comments.
Sounds perfect. Most important is that Summernote can coexist on a page with FontAwesome (and jQuery UI).