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

Bug: unicode symbols displayed instead of glyphs #20128

Closed
1 of 2 tasks
mellodev opened this issue Feb 22, 2024 · 1 comment
Closed
1 of 2 tasks

Bug: unicode symbols displayed instead of glyphs #20128

mellodev opened this issue Feb 22, 2024 · 1 comment
Labels
bug needs-triage This bug needs to be confirmed

Comments

@mellodev
Copy link

Bug description

A few of our projects using FA 6.1.1 exhibit a very rare bug in the browser where all the glyph icons on the page will render as symbols rather than the intended icons. I figured someone here may have seen this before (or know of a related gh issue) and be able to point me in the right direction? Most likely a problem with our build tool, but I wanted check here if this is a known issue.

We have two similar projects, React apps which are built with Parceljs. We include the fontawesome.css and font files in our build/bundle output and host everything from an S3 bucket.

Reproducible test case

No response

Screenshots

Symbols appearing instead of icons:
image (3)

How the page should look:
image (2)

Font Awesome version

6.1.1

Serving

Other (as specified in the bug description)

Implementation

CSS

Browser and Operating System

Chrome on Windows and Safari on MacOS

Web bug report checklist

  • I have included a test case because my odds go way up that the team can fix this when I do
  • I have searched for existing issues and to the best of my knowledge this is not a duplicate
@mellodev mellodev added bug needs-triage This bug needs to be confirmed labels Feb 22, 2024
@tagliala
Copy link
Member

tagliala commented Feb 22, 2024

Hi,

this is a duplicate of #17644 and is related to self-hosting the css version compiled by a "broken" version of Sass (in the meaning that there was a breaking change during a minor release which broke the correct behaviour)

You will find solutions some there, for the moment we can't fix this because it will be a breaking change

Closing here as a duplicate, feel free to comment at #17644

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs-triage This bug needs to be confirmed
Projects
None yet
Development

No branches or pull requests

2 participants