Hi there,
I've been exploring the new Slots feature, but I noticed that slots currently do not pass through the properties of the inner components (instances) placed inside them.
Are there plans to make internal component properties available within slots in upcoming versions? This would greatly improve the flexibility of the new workflow.
Thanks!
Best answer by Celyn_L
Hi everyone — thanks for your patience, and for sharing these examples — they’re really helpful in highlighting how this is showing up in real workflows.
At the moment, component properties (like variants or values) from instances placed inside Slots can’t be controlled or passed through via the Slot itself. Similarly, interactions like hover states on nested components may not behave as expected once placed inside a Slot, even if they work correctly on their own.
This is expected with how Slots work today, and is also consistent with how instances behave more broadly in Figma.
That said, we can see how these limitations impact flexibility — especially when working with interactive or variant-driven components — and the team has heard this feedback and is continuing to explore ways to improve the experience.
As a workaround, if you’re trying to control things like variants or values within slots, using variables and modes can help achieve some of that flexibility.
Really appreciate you all sharing these use cases — they’re valuable as we continue shaping how Slots evolve 🙌
I have a simple component with a hover state. This component is embedded into a slot (which is obviously part of another component). So it’s; Main component>Slot>Nested Component (with hover state). My nested component works fine on its own, but once added to the slot, it loses its hover state.
See video with more detail:
It seems to me that this only works with components that contain nested instances, and the slot doesn't pass them along.
I found a solution, but it looks like a workaround.
https://www.linkedin.com/posts/denys-dod_figma-productdesign-web3-activity-7437838057573138432-xAMs
Hi Everyone, Celyn from Figma Community Support here.
Thanks all for taking the time to share these details and for exploring the new Slots feature.
Thanks as well
I’ll follow up in this thread if there are any updates I can pass along.
Really appreciate you all taking the time to document these cases and flag them here 🙌
Hi everyone — thanks for your patience, and for sharing these examples — they’re really helpful in highlighting how this is showing up in real workflows.
At the moment, component properties (like variants or values) from instances placed inside Slots can’t be controlled or passed through via the Slot itself. Similarly, interactions like hover states on nested components may not behave as expected once placed inside a Slot, even if they work correctly on their own.
This is expected with how Slots work today, and is also consistent with how instances behave more broadly in Figma.
That said, we can see how these limitations impact flexibility — especially when working with interactive or variant-driven components — and the team has heard this feedback and is continuing to explore ways to improve the experience.
As a workaround, if you’re trying to control things like variants or values within slots, using variables and modes can help achieve some of that flexibility.
Really appreciate you all sharing these use cases — they’re valuable as we continue shaping how Slots evolve 🙌
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.