You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
How the page should look:
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
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
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)](https://private-user-images.githubusercontent.com/1292059/307088687-a8e6c608-846f-42ef-a3ac-dc9df7d4cfce.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk5NjU2NDUsIm5iZiI6MTczOTk2NTM0NSwicGF0aCI6Ii8xMjkyMDU5LzMwNzA4ODY4Ny1hOGU2YzYwOC04NDZmLTQyZWYtYTNhYy1kYzlkZjdkNGNmY2UucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTlUMTE0MjI1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9Njg0YmY0NzZiZDJhMjdjZDQ4NjU2N2FjY2ViNTE5YTY4MzExZmRmM2ZkYjYwYzc2ZmM1YjQ3NjYxZjgzN2ZkYyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.DswU5vOfkDfZgKxAKIszyWMuRIhguXKiivBTKg1ECZs)
How the page should look:
![image (2)](https://private-user-images.githubusercontent.com/1292059/307088633-2dffe778-bb8a-45a0-9b0a-9706df1ff43c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk5NjU2NDUsIm5iZiI6MTczOTk2NTM0NSwicGF0aCI6Ii8xMjkyMDU5LzMwNzA4ODYzMy0yZGZmZTc3OC1iYjhhLTQ1YTAtOWIwYS05NzA2ZGYxZmY0M2MucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTlUMTE0MjI1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OTkwYTMyZGU3MTc0NzQzY2NjY2UwMTBmZDAyNzE2OWE3MjRmZDllYzJkMzA4NTlhZDE3YzJmOTFlZWFkNzJmMyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.MyfRkGiuco8CM3zw7-dW6xl8RuRs5yjI9sgVmm7VIVQ)
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
The text was updated successfully, but these errors were encountered: