Slots don't respect nested component's fill values?

Hi ​@MiloW, Celyn from Figma Community Support here.

Thanks for taking the time to share this feedback and call out the specific behavior you’re seeing with width and height not filling the slot area as expected.

I’ve shared this with the team so they’re aware of how this is affecting real workflows — this is helpful context for the team as they evaluate the current behavior.

Appreciate you raising this again.

Hello, yes, I know, I decided to write about it in two places, also for the people.

We’ll continue.

Our team is maintaining our slot component work-around that existed before the native release for this reason.

Tip: Although annoying, we have found that a manual placement(drop the instance into the canvas next to your slot, drag and drop into slot) of the ‘slot content’ instance honors the auto layout defined at the main slot-content component - for whatever reason.

We are also experiencing this issue. We have some components set to fill container within their component frame. When inserting those components into a slot, they add as a fixed width instead of filling the slot container like expected. This behavior adds an extra step that our designers need to do to properly use those components as they are coded.

However, if I drag an instance directly from the main component into the slot, then it respects the fill container and it works great. It doesn’t respect the fill when inserting from the “+” button on the slot or the quick insert menu.

Hey ​@MiloW — I checked in with the team to get more clarity on the “Fill” behavior you’re seeing and wanted to share a quick update.

Could you help confirm if you are expecting the Fill settings to be inherited from the main component of the inserted instance, or from some configuration within the Slot itself?

For context, instances don’t inherit the Fill settings from their main components when inserted, and this same behavior extends to Slots as well.

​@Ben64 ​@Straton_Roberts — thanks for sharing your feedback here as well. I’ll be sure to pass this along to the team 🙌

​@Straton_Roberts has exactly the problem although I am not really able to drag and drop stuff as my component having the slot gets “crazy” - it doesn’t insert into the slot, it inserts the item wherever it wants…

IMO there should either be a switch for a slot “preserve added instances features” or something… or it should respect them just like that, IMO this is expected.

Just also wanted to mention these as well - will create new posts if I can’t find anything related:

• Cannot select a variant as a preferred instance. Kind of a drag as designers would only know there is a specific variant to be used by documenting it in written word. A preferred variant instance would clear up the communication without so much documentation.
• Slots need something like an empty state that hides the slot by default if not filled instead of relying on booleans to hide them