Hi everyone, I recently had a problem with interactive animated components when user testing them, since our users didn’t have the custom fonts installed on their machines the animations ended up glitching.
I “fixed it” by sending the fonts for them to install.
Since this is not normal behaviour with this feature, I’d like to report this as a bug if possible.
I’m running into a same/similar error. We have our custom typefaces installed via “Shared Fonts” feature.
On the initial load component displays correctly, after an interaction that involves switching a variant (i.e. hover) I get a message “Some missing fonts were replaced” and the typefaces switches to some fallback.
This Thursday is the scheduled time for this fix to roll out. We won’t be able to force-install a font on another designer’s computer (e.g. in case they don’t have the permission), so we resorted to a fallback font to minimize glitch. Let us know if it’s not quite the fix you imagined.
Same issue here. This is especially noticeable with font awesome icons. In some components—not all for some reason—and often with the hover/mouse enter states, the font awesome icon turns into the text (for example an up arrow icon will become the phrase “up-arrow”) and it really breaks the design. I tried reinstalling the font on my end, making sure it was the most updated version, and this did not help.
The issue still persists. Like some others, we use FontAwesome for all our icons. We can’t share prototypes with the rest of the business anymore as they look broken. It’s only on components with interactions. The font works fine until you interact.
Thanks everyone—if the font is only local to your computer, we won’t be able to calculate all the different states for other users. We are incrementally adding ways for this to work in more cases. Sorry for the trouble, and thank you for the feedback! Especially useful to hear about the font-awesome use case.
Hello @Andrew_Heine, as @Camilo_Bolivar mentions this was not an issue when the beta for interactive components was released. If this changed due to performance —or other— reasons, is this what we should expect from the final release? Thanks!
I’m finding this is still happening; hopefully this will be fixed soon because many of my files prior to two or so weeks ago were working great. Now I am going back and finding work arounds for the issue (like outlining fonts, etc), but if this is fixed that would be awesome.
Is this going to change on the final release? I work on an agency so sharing fonts with every client is not super doable, Would be nice to know if doing these is reliable in the long term.