Overriding one element inside a slot marks the entire slot as overridden

Agreed. One small change to one element inside the slot instance marks the entire slot as overriden and no longer inherit its master’s properties - essentially making it similar to being detached. Therefore slots is not very useful at the moment.

Hi there,
 

Thanks for the detailed breakdown. I tested this on my end, but I wasn't able to reproduce the issue.

In my test, when I overrode a single instance inside a slot, the other elements within that same slot continued to receive updates from the main component as expected.
 

Since I wasn't able to replicate this on my side, we'd like to take a closer look at what’s happening in your specific case. Could you please reach out to our support team?

You can do this by clicking the "?" icon (Contact support) directly within the file where this is occurring. The chatbot will walk you through the process, which will allow our team to look into your specific case and provide more tailored guidance.

Here’s a guide you can refer to:  What to share in a bug report to Figma Support 

Thanks,

I’ve recorded a quick video of my test here for you:
 

​@Junko3 

No problem, I have recorded a video of my own to describe the issue​​​​​, using the example component in Figma’s Slots Playground file. Here are the steps:

1. Create an instance of the component that has a slots frame
2. In the master, change the color of the button, the instance still follows and change its button color accordingly
3. Now in the instance, try changing something that is not related to the button, for example, the description text. Just add a single character to it.
4. Now go back to the master and change the button color. Now the whole slots frame in the instance has been marked as overriden and the button color in the instance doesnt change accordingly.

Hope it helps!

Hi ​there!

Thanks for the clarification and the video! My apologies for the misunderstanding earlier.

Following your steps, I was able to replicate the issue on my side with a component slot that contains default content.

I’ve checked internally, and it appears this is a current limitation.

Once you modify the content in a slot in an instance, it is treated as an override; therefore, it will no longer receive updates made to the default content from the slot in the main component.

I’ll go ahead and move this post to the "Share your feedback" category and pass this along to our team, as I understand how important it is for the default content updates to be reflected.

Thanks again for your input!

Thank you! I look forward to this improvement.