Skip to main content
Marshall1
New Member
September 13, 2024
Solved

BUG: Auto-layout issue in Overlay when using Variable Mode

  • September 13, 2024
  • 3 replies
  • 262 views

When switching variable modes in an overlay the new values do not follow the autolayout rules.

I think this is a bug because closing and reopening the model will fix the autolayout issues. To fix this I included a duplicate of the modal and switch between them when changing the variable mode.

Let me know if anyone is interested in links or images.

This topic has been closed for replies.
Best answer by Celine_

Hey everyone,
To give visibility on this issue, our engineering team have also confirmed that this is a bug.
However, we want to be transparent with you that this will not have an immediate resolution as we need more time to investigate this.
 
While we can't promise a quick fix, please know that our engineering team is aware of the issue and will work towards finding a solution in the future.

We appreciate your understanding and patience in this matter, thank you!

3 replies

Rodrigo_Diaz_Salvadores
New Member
January 27, 2025

I encountered the same issue today. It seems like the autolayout properties aren’t immediately respected when the mode changes. If I manually change the size of the parent component, then the change seems to be noticed and it immediately readjusts itself. 

I have found this happens if the frame that doesn’t resize is a component instance and uses any kind of variable (no matter if it is color, spacing...)

Celine_
Figmate
Community Support
January 27, 2025

Hi all,
This looks odd, thank you flagging this!

@Rodrigo_Diaz_Salvadores , I see in the backend that you have already reached out to the support team. We are waiting for your response for further investigation. Please check your inbox (for your reference, your ticket number is #1239080).


Thank you

Celine_
Figmate
Celine_Answer
Community Support
February 12, 2025

Hey everyone,
To give visibility on this issue, our engineering team have also confirmed that this is a bug.
However, we want to be transparent with you that this will not have an immediate resolution as we need more time to investigate this.
 
While we can't promise a quick fix, please know that our engineering team is aware of the issue and will work towards finding a solution in the future.

We appreciate your understanding and patience in this matter, thank you!