Hi all! The new Slot has just been released and I’m looking into replacing the selfmade slots in our library with the new released slots. But I’m already walking into my first problem with the new slots.
I have a component where we have 2 slots with the same instance swap property. These slots have boolean variables added to them so they will be hidden/shown on different breakpoint modes.
With the new slots I have not found a way to use the same slot property twice in the same component yet, other than keeping our current setup for now, does anyone have a good idea on how to solve this?
Solved
Using multiple slots in 1 component with the same slot property?
Best answer by djv
Hi All, thanks for your patience!
I’m Denise, and I work with Gayani on the Community team. We confirmed that this is a current limitation of Slots: two slots within the same component variant cannot share the same slot property. Slots can share a property across different variants, but not within the same one.
Here's what we know so far in terms of temporary solutions:
1. Use variables instead of component properties
- Variables are still supported inside slot content. If you're using boolean variables to show/hide slots at different breakpoints, binding those to variable modes (e.g., a size or breakpoint mode) rather than component property references may get you to the same result.
2. Keep component property bindings outside the slot boundary
If any logic relies on component properties, keeping those bindings on layers outside the slot is the most reliable path right now.
Also, as
That said, I’ve updated this topic into a feature request, and this feedback has already been shared with the team. Hope this helps in the meantime!
Hey
I’ve shared your use case with the team internally to better understand whether this is a current limitation or if there’s a recommended workaround. I’ll update you here as soon as I have more clarity.
Really appreciate you taking the time to explain your setup so clearly
I found in the latest update that there is a conflict with the new slots property if any object adding to that slot contains an instance-swap property. Once I changed the base component from being an instance swap option it worked again. And I could add as suggested components the same options to various slot properties as long as they did not contain that instance swap. I hope this gets fixed, but it helped me for now.
Following as this functionality is something we need as well.
Hi All, thanks for your patience!
I’m Denise, and I work with Gayani on the Community team. We confirmed that this is a current limitation of Slots: two slots within the same component variant cannot share the same slot property. Slots can share a property across different variants, but not within the same one.
Here's what we know so far in terms of temporary solutions:
1. Use variables instead of component properties
- Variables are still supported inside slot content. If you're using boolean variables to show/hide slots at different breakpoints, binding those to variable modes (e.g., a size or breakpoint mode) rather than component property references may get you to the same result.
2. Keep component property bindings outside the slot boundary
If any logic relies on component properties, keeping those bindings on layers outside the slot is the most reliable path right now.
Also, as
That said, I’ve updated this topic into a feature request, and this feedback has already been shared with the team. Hope this helps in the meantime!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.