![]() If you're hosting yourself and using only certain styles, you will need to add an additional CSS file. If you need support for Font Awesome 4, you can load additional files that provide the same level of translation. If you're hosting yourself, our SVG + JS framework handles translating any Font Awesome 5 icon names, style syntax, and CSS pseudo-element references automatically. This kit will also do the same for any Font Awesome 4 icon names or font-face CSS rules. If you're using a Version 6-based kit, it will automatically translate any Font Awesome 5 icon names, style syntax, and custom Font Awesome CSS rules to their v6 equivalent. ![]() Here's how and when the above features to turn on that compatability when using Font Awesome 6 on the web… Kits (SVG + Web Fonts) This is useful when writing custom CSS or using pseudo-elements ![]() We make sure that your project's CSS points to Version 6's Web Fonts and renders the latest and greatest icons. We've switched to full style names, but icon references that use the old style syntax will still work We've bundled the following by default… What We DidĪny icons that had their name changed in Version 6 will work and render as expected when referenced by their old nameĪdded Aliases for v4/v5 Icon Unicode ValuesĪny icons that had their unicode value changed in Version 6 will work and render as expected when referenced by their old value We've tried our hardest to make Version 6 backward compatible with Font Awesome 5 and Font Awesome 4 too! Whether you're using Kits, components, hosting things yourself, using Web Fonts, or SVG + JS, we've done a lot to translate icons in existing projects to Version 6 automagically. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |