When I “Detach instance” on the filter panel, it behaves as expected
Does anybody have the solution for this? It feels like it’s a really common use case - I’m trying to achieve a similar thing and I’m getting all sorts of bugs. The issues with expanded components overflowing each other for me had something to do with “constraints” (top left) hiding that element at the top of the list. How did I solve it? I hit CTRL+Z until “constraints” went away. Not exactly a solution! Currently, none of my sub-nav elements hold on to their unique text labels, they just revert to “sub-nav”… should this type of accordion nav component really be this difficult? You could throw it together in minutes with Bootstrap or another free, off-the-shelf CSS/JS solution!
I’m having the same exact issue. I’m using accordions in a main menu. Similarly, if I detach instance of the main menu’s component it works. But, this is for a design system, so I can’t have everyone detaching instances.
Same issue here for the last year. Very counter intuitive that the accordion instance cannot prototype correctly. Detaching the instance works, but creates extra work.
Hopefully Figma can address this soon
I know this is late. There’s something wrong with your layers and Figma is trying to preserve overrides.
Example: Figma preserved the height of this component (probably the component’s height is fixed).
That’s also the reason why detaching it worked, because it didn’t preserve overrides after the detachment.
My advice is to check: (1) layer names, (2) Constraints if not in auto-layout, and (3) auto layout properties properly from the very start so that it’ll work as planned.
(I’ve used the same implementation you’re trying to do in this vid)
Thank you for your input @Raphael_M . This helped me solve it.
The problem was that my accordion items had a fixed height set and not “hug”.
