Skip to main content
Solved

FIXED: Bug with Multi select / edit text and library font styles

  • March 7, 2024
  • 6 replies
  • 380 views

Paul_Soultis

Hi team,

With the new multi select/edit text, when using this function across different breakpoints the fonts styles are being replacedto match the edited field.

If the edit prompt field is in a desktop frame it will replace our mobile frame with the same desktop font styling.

Is there a way to make edits to the copy without the styling being replaced?

Best answer by Paul_Soultis

Hi @Celine_Figma it looks like a fix was deployed and the multi-edit is working without changing the font style.

Thanks for the support!

This topic has been closed for replies.

6 replies

Celine_
Figmate
  • Community Support
  • March 8, 2024

Hey Paul! Thank you for your feedback. This is intended for now, but we will pass your feedback to the team for improvement!


Paul_Soultis
  • Author
  • New Member
  • March 11, 2024

Thanks, @Celine_Figma appreciate the response. Would you happen to have a shareable roadmap of what the intention will be in the future?

Also, can you suggest any temporary workarounds after a multi-select-edit to prevent font styling changes without the need to manually change the text fields for the mobile breakpoints back to the mobile-specific font style?

Thanks
Paul


Celine_
Figmate
  • Community Support
  • March 11, 2024

Hi Paul! To be transparent, the team is working on it now to implement a fix, although it is an “intended” behaviour - while I can’t share any specific ETA for the moment. Stay tuned, and thanks for your patience in the meantime! 🙏


Paul_Soultis
  • Author
  • New Member
  • March 11, 2024

Thanks for your transparency @Celine_Figma. I’ll keep an eye out for the fix.


Paul_Soultis
  • Author
  • New Member
  • Answer
  • March 18, 2024

Hi @Celine_Figma it looks like a fix was deployed and the multi-edit is working without changing the font style.

Thanks for the support!


Celine_
Figmate
  • Community Support
  • March 19, 2024

Hey Paul!
Yes, I confirm a fix has been deployed. Thank you for following up!