Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fontawesome 6.1.1 to 6.5.1 for remove Font console error #1090

Closed
willouch opened this issue Mar 30, 2024 · 2 comments · Fixed by #1096
Closed

Fontawesome 6.1.1 to 6.5.1 for remove Font console error #1090

willouch opened this issue Mar 30, 2024 · 2 comments · Fixed by #1096
Assignees

Comments

@willouch
Copy link

Winter CMS Build

dev-develop

PHP Version

8.1

Database engine

MySQL/MariaDB

Plugins installed

No response

Issue description

In Backend, Fontawesome cause error message.
Up to Fontawesome 6.5.1 resolve Font console error :
downloadable font: Glyph bbox was incorrect (glyph ids 5 9 10 12 13 15 16 33 49 59 60 61 72 76 81 83 84 85 88 91 92 97 101 102 103 104 106 107 109 118 120 121 122 124 134 135 136 137 139 141 143 145 146) (font-family: "Font Awesome 6 Free" style:normal weight:300 stretch:100 src index:0) source: /webfonts/xxxxxxx.woff2

Steps to replicate

Font Error message in logs browser console from Backend

Workaround

No response

@willouch willouch added needs review Issues/PRs that require a review from a maintainer Type: Unconfirmed Bug labels Mar 30, 2024
@arvislacis
Copy link
Contributor

This is FontAwesome issue happening in Firefox browser: FortAwesome/Font-Awesome#19925

Nothing critical but updating font files to FontAwesome 6.5.1 version will fix this.

@bennothommo bennothommo self-assigned this Apr 2, 2024
@bennothommo bennothommo added Type: Bug and removed Type: Unconfirmed Bug needs review Issues/PRs that require a review from a maintainer labels Apr 2, 2024
@LukeTowers
Copy link
Member

PR welcome :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants