Insert component is buggy: It just inserts the component in a random frame

Ask the community
1

When I select a frame and add a component via the button in the top menu, I expect the component to be inserted in the frame I selected in the left sidebar. But Figma for whatever reason just throws the component into a random place in the frame tree. I then have to look where it went and drag it to its intended place. Sometimes it ends up in a nested frame, sometimes just somewhere in the top level of the page. Same with icons I insert via plugins.

Why is that? Dear Figma team, can you please fix that? Or does anyone have a solution?

Before I insert the “Pagination” component I have selected the frame (Slide3) I want to place it in:

Screenshot 2023-10-31 at 21.38.42
Screenshot 2023-10-31 at 21.38.42668Ă—772 25.7 KB

But it ends up somewhere completely unexpected:

Screenshot 2023-10-31 at 21.38.53
Screenshot 2023-10-31 at 21.38.53668Ă—808 28.6 KB

2

Hey @OleBerlin, thanks for flagging this!

This definitely seems odd, and not the expected behavior. We’ve flagged it internally for our team to investigate. Hopefully, we’ll be able to share an update soon.

1 Like
3

Just +1’ing this. The component just drops into some random frame anywhere on the page. Sometimes I put one in, and have no idea where it goes and never end up finding it.

1 Like
4

Hey @Ian_Palmgren, sorry for the trouble!

Our team confirmed that this was a regressive bug that should have been fixed. We just tried to reproduce in the desktop app and browser and components seems to be pasting into the selected frame on the canvas as expected.

Is this happening for you consistently? What OS are you using, and are you using Figma in browser or the desktop app?

5

Thanks for checking in @dvaliao! It’s definitely inconsistent – sometimes components go exactly where I’d expect, and sometimes I have no idea where they are. I’ll see if I can screen record the next time it happens to me.

I just experienced this yesterday, so I know it’s still happening frequently. I ended up having to go to the library to get the component since I was working in a huge file (with tons of components of the same name already been utilized in the file) so I couldn’t ever track down where they were going.

1 Like
6

Thanks for the context, @Ian_Palmgren!

If you’re able to consistently reproduce or get a screen recording, that would be so helpful for the team.