still the same issue, will it be solved?

Experiencing the same problem with interactive components and FontAwesome text icons breaking in prototypes. I’ll have to let my design team know they cannot use interactive components until this is resolved. Hopefully a fix is coming soon? We’re so excited about interactive components and are in the process of building out a new design system.

It looks this issue is fixed. I don’t see this issue now. Is there any official announcement about this?

This problem still persists, at least on windows. Chrome mac seems to be working.

Also experiencing a similar when a few of my colleagues and myself are using different computers i.e. Windows and Macs. We all have the same fonts families downloaded but as some only have Windows others Macs we have the same font but different formats installed.

Able to edit the designs but only when we replace the font families. Getting pretty tiresome seeing the missing font warning message. Anybody know a work around this? Other than we all get Macs ^_^.

The problem persists still on Chrome, Windows.

I am still experiencing this issue as of today.

When fonts are not installed (= custom fonts (no google font) that are not included in Figma by default) the interactive components in the prototype go absolutely bonkers.

Text is casually disappearing and elements are moving or indent.

If interactive components are not used (= everything is static) there are no problems and the fonts get displayed as expected. So the bugs only appear in combination with interactive components.

While working in an agency context we want to utilize interactive components in prototypes but our clients may not see our designs correctly or even worse they think something is broken and we’re not aware of that. Only “workaround” is still to ask the folks to install the fonts on their machine but this is not only a licencing problem but also a huge effort that should not be required.

Never had any of those problems with Sketch Web views since they are able to embed the fonts properly.

Yeah, I’m experiencing the exact same problem still: while component variants with dynamic text work fine on MacOS (for us designers), this is breaking in Windows (resulting in blank text).

Can the Figma team respond as to when this bug will be fixed? This is resulting in having to create workarounds where we detach thenrecreate these components but with static/hard-coded text (in the case of “auto-filling” text fields).

Thank you for any help you folks can offer or information you can share, timeline-wise!

I’m also still experiencing this problem

This still appears to be an issue, which is very problematic when it comes to sending the prototype for testing. It’s causing entire text blocks to disappear, making the experience and the prototype seem broken. Any update on a fix for this? It seems like embedding the fonts in prototypes would be the logical solution.

This is still a recurring problem for us. The only way to resolve this is to install the required font files plus the Figma Agent. This is not a suitable approach for our customers with them being mostly local authorities with extra strict IT policies.

Any update on when this might get fixed?

I’m experiencing this too. Sometimes text will totally not appear. Sometimes I can’t click into a text field to edit it. In prototype mode, we often get the error “Some missing fonts were replaced”.