We're migrating our design system to Slots, and, like most designers, we're using slot placeholders and instance swaps as a workaround. As a result, we now have multiple components with placeholders that have been replaced by local instances containing content.
When we wrap or convert component frames to slots, the override resets.
BUT this is dependent on the account. In my work account, it is resetting the swapped instance. However, when my colleagues apply the same wrap to the same component, the resetting does not occur. I also tried in another private account, and resetting also does not occur.
See the video attached.
Is it a slow rollout of the update to Slots or is it a bug?
Question
Wrapping/converting to slots breaks overrides but not for all
Hi
Thanks for your post - this is a really great question. Are these components coming from a published library, and is the file where it does override the instance the library file itself? In your video, I wasn’t sure if you just duplicated the file or if one is your library and the other just used components from the library.
Since I’m not sure what the expected behavior is here, I reached out internally to find out and I’ll reply when I hear back more information. Regarding slots in general, it has been fully rolled out now so that shouldn’t be a factor.
In the meantime, let me know if you see anything different or discover something yourself.
Hi again
I just heard back from our team and the intended behavior is what you see in your work account; we actually just released that change which also explains why it seems inconsistent, and why you see the message just above the toolbar that states “Properties removed from layers in this slot”. If your colleagues reload their tabs, they will see the same behavior you see. For a bit more info, you can also read this section of the slots help article.
Its very hard to understand why Figma would silently remove this functionality.
My experience is now that the instance swap is removed in the variant level, but not at the variant set props, its just marked as “unused”. But even worse, every single modified instance using the previous technique will break.
This will making the migration process 100% breaking changes. Is there any rational for the change to help us understand?
Hi
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 variant swapping - changing the size mode from S to M, as an example. We have a section on binding variables to variant instances in our help article along with a video, too.
I’m not sure what steps you are following when migrating, but It might also be helpful to view our guide on migrating to slots since it provides a couple different paths to do this. Each path includes pros and cons to help you best know which will work better for you.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.