Stacking icons is not appearing correctly
See original GitHub issueI am using this code:
<fa-stack>
<fa-icon [icon]="['far', 'circle']" style="font-size: 8px;" stackItemSize="2x"></fa-icon>
<fa-icon icon="file-alt" stackItemSize="1x"></fa-icon>
</fa-stack>
And I am getting the following result:
How can I get the document icon to center inside the circle? I have already tried text-align and forcing a margin, but none work.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
fontawesome: stacked icons not displaying correctly
If you are talking about just minor misalignment (a pixel or two), then that is unfortunately the nature of some icon font glyphs....
Read more >Arch: Candy Icons not working properly - Unix Stack Exchange
So, recently installed candy icons but not get them to work properly.In my user directory, only the icon for Desktop folder is applied....
Read more >Examples - Font Awesome
To stack multiple icons, use the fa-stack class on the parent, the fa-stack-1x for the regularly sized icon, and fa-stack-2x for the larger...
Read more >Topic: Stacking Icons with x-icon or Font Awesome - Themeco
I'm not really sure if I understand you correctly? did you mean to display the icons in line? If so you should add...
Read more >Why are some desktop icons not displaying correctly?
Did you create those desktop files? You need to edit them in a text editor, and apply appropriate icons. · Firefox dev was...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@devoto13 that is indeed correct. I updated the stackblitz and removed the css file and the stacked icon looks good now.
Thank you for pointing that out.
Closing as the problem was caused by a user error. Please open a new issue with minimal reproduction if you still experience the problem.