Resolution Status of the Duplicate Font Variable Bug | Relume Community

Resolution Status of the Duplicate Font Variable Bug

Did this duplicate font variable bug get resolved? https://community.relume.io/variable-attachment-causing-class-sync-issues-2J7V1swY5fL5

10 comments

Matt J.
·
Alex D. would you mind sharing a read-only link?
Alex D.
·
Matt J. I can't share my current project, but in a nutshell, it's the issue that if you use a font variable in Webflow on a Relume class (e.g. on .heading-style-h1) and then paste a Relume component using the same class, it creates a duplicate class on paste. Looking through the support forums, it's been identified as a bug a few times last year, but there's no mention of a resolution yet.
Matt J.
·
Alex D. can you DM the read-only? it helps a lot and it could be a dozen or so reasons and at least half of them can be confirmed/verified by looking at the read-only.
Darren H.
·
Matt J. chiming in here with a +1 on this issue. Been driving me crazy trying to figure out why classes are duplicating seemingly at random - I have a clean starter project cloned from the base Relume starter, all that I've done is add variables panel setup and linked up global styles like typography to them, and make a few components. With any component pasted in, heading-style, text-size, and button styles are duplicated just about every time. Read only
Matt J.
·
yeah, font variables are not supported by class sync with the current version of the extension or the webflow app, so I would avoid using font variables for now.
Matt J.
·
We're hoping to be able to do this soon but its not 100% on us at Relume
Darren H.
·
Got you - simple enough workaround by binding these with custom code, but will be nice to get cleaned up! The main issue was not knowing why it was duplicating.. glad to have it figured out!
Matt J.
·
yeah, for sure, we could have done a better job at communicating that but its a bit of a tough one.
Darren H.
·
All good. I appreciate the response!
Darren H.
·
·
Is there any update on the font variables issue above? I believe it's still an active bug