Skip to main content
aden
aden
New Member
April 21, 2026
Question

Child components encapsulated in slots cannot be edited continuously.

  • April 21, 2026
  • 1 reply
  • 64 views

When encapsulating components, if a child component is placed inside a slot, after setting the toggle switch for the child component, the slot will be marked as edited. This causes all the controls of the child component to disappear. The expected behavior is that editing the child component (such as turning off an icon, removing a border, etc.) should not be considered as editing the slot, allowing continuous editing of the child component.

1 reply

Figmate
Junko3
Figmate
April 22, 2026

Hi ​@aden, 


I understand you're experiencing an issue where modifying a toggle on a component inside a slot causes the slot to be marked as edited, making the child component's controls disappear.
I tested this on my end — once I changed a boolean property on an instance inside a slot, the slot was marked as "modified" and the instance no longer received updates from the main component. However, I was still able to toggle the property back on the instance.


Without more details about your specific setup, it's hard to say for certain, but what you're seeing may be expected behavior.

To keep slot behavior consistent, component properties are no longer supported on layers inside a slot. If a layer with a component property reference is moved into a slot, that reference is removed, and content within slots will not be changed by variant swaps.
 

If you're open to it, our team take a closer look at what’s happening in your specific setup.

To do that: Go to the  Support Hub  / Click Start a chat / Type “Report a bug” /

Include in the form:

  • a direct URL to the file
  • share view access to the affected file with support-share@figma.com (our official Support account) so the team can take a closer look. You won’t be billed for this access.
  • any screenshot or video recording when you encounter the issue. This will help our team to better visualise and reproduce the issue on their end.

In the meantime, If you need flexibility inside slot content, variables are still supported. Depending on your setup, it may also help to keep component property bindings outside the slot boundary. By binding variables to variants and colors, you can achieve the intended effect by changing modes rather than directly swapping variants.

Here is the link to the section on binding variables to variant instances in our help article and here is a video.!-->

 

Thanks,

!-->

Terms & ConditionsAccessibility statement