-
Notifications
You must be signed in to change notification settings - Fork 12.2k
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
Bug: Glyph bbox was incorrect in the Firefox dev console #19925
Comments
Confirm bug happens on Firefox (tested with 118.0.1) but not on Chrome (tested with 117.0.59.xxx). |
Thanks, folks. We've heard this report from a few folks. It looks like the Firefox team introduced a new tolerance check in their recent build. There are some glyphs that extend slightly beyond the bbox area (this is related to how curves are sometimes drawn differently between OTFs, TTFs, WOFFs, SVGs, etc). The good news is that there should be no issue with the icons from a visual standpoint (the cropping is so minute, that it's imperceptible for the most part). |
@sensibleworld This is also occurring in v4. Can we get a fix there too and a bump to 4.7.1 for the npm package? npm's stats show over 2 million downloads of 4.7.0 in the past 7 days. |
v4 is in EOL and that npm package is not official. You can try to get in touch with the author |
Same warning with :
|
Unfortunately the GitHub repo that published the npm package does not have an issues page to report this. Unless @juliankrispel sees this and is willing to modify the font files and do a new release, I'm guessing those contributing to the 2 million+ downloads a week will need to either live with the warning, or switch to something else that is maintained. |
I use https://github.com/FortAwesome/font-awesome-sass and am seeing the same issue. |
Same with font awesome pro 6 (latest) and subsetter compiles |
Bump :) |
+1 |
Bump!!! |
This is a feature not a bug 🐛 . |
The fix has been completed and will appear in a forthcoming release of Font Awesome. The fix will be present in the official fonts for that forthcoming release, as well as fonts built when downloading or subsetting kits from fontawesome.com. |
Awesome, thank you. |
Wonderful, greatly appreciated. |
Great news. |
Has that happened yet? If not, do we have an ETA? Thanks! |
Yes, it's fixed in Font Awesome 6.5. |
What about fixing this in version 5 which is an LTS that should still receive patch releases? |
Not sure this qualifies as a "critical bug fix", at least not yet. |
Even if not critical, seeing this message a hundred times a day is annoying and distracts developer's attention from actually important notifications. |
I still get this error
|
I also got this error until I defined the font-weight explicitly in the css: |
Tengo el mismo problema, con laravel 11, inertiaJS, mozilla firefox developer, pero solo es cuando ocupo la debugbar de laravel, siempre me aparece esto: |
Could you say what version of Font Awesome is being loaded in these cases where you still see the warnings? If you're seeing this again in Font Awesome 6.5 or newer, then there's been some other change, or a regression that I'd want to investigate. If you're still seeing the warnings on Font Awesome 6.4.2 or earlier, then that's to be expected. Here's a CodePen that loads FA 6.5.0. In Firefox, I don't see the glyph box warnings for this one. Expected. Here's a CodePen that loads FA 6.4.2. In Firefox, I do see the glyph box warnings. Expected. |
my package.json information: |
what is With a search on GitHub, I suppose this is a third-party component: https://github.com/search?q=PhpDebugbarFontAwesome&type=code which is vendoring Font Awesome as a base 64 encoded file I guess that this component should be updated too |
@deividfirewall your Therefore, those glyph bbox warnings have nothing to do with your What @tagliala shows is a common scenario in environments like this. There may be multiple components in the system using Font Awesome in various ways. Sometimes these conflict or produce unexpected behaviors. I created another CodePen using FA 4.7.0 Webfont/CSS, and it does show the glyph bbox warnings in Firefox as well. So it's very likely that |
You're right, I tried to solve my problem with Tagliala's solution, however I didn't find the code in my project, maybe it's because php-debugbar consults its API directly, anyway I appreciate the support and that they clarified to me that the problem is not in my project. |
Bug description
When using FontAwesome v6 with Firefox (118), I'm seeing many warnings about FontAwesome glyphs in the console.
For example:
According to this ticket in Firefox's bug tracker, this is not an issue with Firefox, but an actual bug in FontAwesome font definition.
Reproducible test case
https://codepen.io/Thomas-Chapeaux/pen/gOZdpMV
Screenshots
Font Awesome version
v6.4.2
Serving
Kit
Implementation
CSS
Browser and Operating System
Web bug report checklist
The text was updated successfully, but these errors were encountered: