font awesome / unicode encoding issue fix #635
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also fixes incorrect font-family name for Font Awesome @ line 376
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
PR fixes issue #634 and fixes incorrect font-family name for Font Awesome @ line 376.
Screenshots
Available in #634
Types of changes
Minor changes to widgets/frontend.css to fix a encoding / rendering issue.
How has this been tested?
Tested on a clean install of WordPress 6.1.1, Elementor 3.9.2 and Elementor - Header, Footer & Blocks 1.6.13
Checklist: