menu
announcement

Spectrum is now read-only. Learn more about the decision in our official announcement.

Figma

Figma is the first collaborative UI design tool built in the browser. Join our growing community and kick off a conversation!

Channels
Team

BUG: Sometimes nested components detach in a component instance.

July 23, 2018 at 8:07am
The Figma community has a new home. This thread is preserved for historical purposes. The content of this conversation may be innaccurrate or out of date. Go to new community home →

BUG: Sometimes nested components detach in a component instance.

July 23, 2018 at 8:07am
I have a few screens that I have made into components, which have nested components(nav elements, buttons etc) in them. When I instantiate these screen components some of them behave as expected (ie: all the nested components stay attached to their master) but for about 30% of them the instance detaches all of the nested components, kinda rendering the whole component useless.
The strange part is it is always the same screen components that do this, even if I detach and recreate the component. Which makes me think their might be something inherent to these particular frames that cause this. I just can't see any differences between those components, and the ones that function as expected.

July 23, 2018 at 8:20am
Also, should note, I am dragging the instances from the components panel.
Not Copy/Pasting
UPDATE: Manage to work around this. I tracked down the particular nested component that was common to all those screens. Then I removed it from the component, updated it and synced the changes to the instance, then re-add it to the component, update and sync again. Now all the instances are relinked.
Weird.

July 24, 2018 at 9:32am
Well, I noticed that (while copy/pasting) only swapped instances detach. Maybe dragging components that already have swapped instances in them is basically the same thing.
like-fill
1
For example, if I drag two instances of "input" component and then swap one instance here https://imgur.com/IC00AAF and then duplicate the frame the original instance will remain attached and "swapped" will be just a frame.
I think if you have components that rely on the instances of other components that have been swapped that may be the case. Although I don't understand why it happens.

July 24, 2018 at 6:00pm
This is a major problem for my team. We're constantly copying and pasting components with overrides across files. They detach and designers don't notice, resulting in a big mess that's difficult to recover from.
Can someone at Figma explain whether this is a bug? Is there a known workaround? Are we "doing it wrong"?
like-fill
5

February 4, 2019 at 8:45pm
Any updates on this? It makes utilizing components really difficult.
Having a particularly frustrating day with it.
I did find a POSSIBLE hack that prevents this.
like-fill
1
If you group the offending sub-components. They import correctly.
like-fill
1
But as says sometimes teammates can miss a component that is broken, and lose the connection to the design library.
Thanks for the workaround ! I still think this bug should be fixed as it impacts our design system.
like-fill
3

February 5, 2019 at 9:26am
This should be a top priority, it has the potential to completely destroy consistency in a big project making it impossible to manage.
like-fill
1

February 5, 2019 at 7:43pm
And the latest related bug is that the components are in the library, and don't show up.
Switch/On and Switch/Off just don't show up.
Nothing...

February 6, 2019 at 5:31am
Annoying also how, once a component is detached - turns into a frame and that frame name appears on canvas.

February 6, 2019 at 1:38pm
Basically I have a couple of days worth of work turn into a complete mess because of this. The worst part is: what now? I can't trust to work with components as things stand.
like-fill
2

February 8, 2019 at 2:45pm
What's everyone doing about this? I can't believe that there's no official communication from Figma regarding this matter. It's literally turned weeks of work into a complete unusable mess!!!!
Figma has replied directly to me a few times about it, and I had a call with them post-organization feedback. They said it was a complex problem that they are working on fixing.
Edited
like-fill
3

February 11, 2019 at 11:27pm
Same problem here. Been struggling with this for a few of weeks. Another even more concerning bug is that for no apparent reason elements in the component instances suddenly display incorrectly, with #000000 color, often the background in #00FF00. Sometimes if I nudge the problematic elements 1px and back in the component source, then export, it displays correctly. But just as often this doesn't work. What's really worrying is that the bug doesn't seem to be reproducible, problem just appears out of nowhere. Figma, please please fix this, it's destroying our workflow.