Skip to main content

Currently I’m missing the feature to collapse the properties of nested components in the right side panel in Figma easily.




  • Imagine you’re building a card.




  • You’re nesting different components within that card - let’s say 5 nested components.




  • Every nested component has properties.




  • These properties will be revealed in the card component.




  • When using the instance of that component (as a user), you’re instantly overwhelmed by the option of properties, which are initially shown in the right side panel.




It would be great, if one could collapse all nested properties with just one click or shortcut, instead of manually closing one by one.



Having clear visual indicators for collapsed nested components and some sort of visual hierarchy, would be even better 🤩


Cheers,

Katrina

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.


Currently I’m missing the feature to collapse the properties of (all properties inkl. nested properties) components in the right side panel in Figma easily. I would like to have a setting (switch) for how I want it to be default. Collapsed or expanded. This explains it really good. Collapse properties of nested components Figma, can you just fix this please 🙂


Came to this suggestion specifically because the new UI is in desperate need of two things:



  • The ability to collapse the properties section of the right-hand panel entirely

    Extremely high-use tools such as position, auto-layout, and appearance are extremely hard to get to most of the time now

  • Properties desperately need a visual hierarchy so that we know which properties apply to which nested element

    Anything with 2 or more levels of nested properties exposed becomes extremely difficult to navigate, especially when sub-components are named similarly or using default values


In an ideal world, we’d also be allowed to selectively show/hide which properties are exposed via a nested component to reduce clutter and retain control over how components are used (this was raised in a different suggestion already).


Reply