Skip to main content
Stefan_Pilipovic
Feb 11, 2021 2:31 PM UTC

Disable auto-nesting/auto-reparenting while moving objects

  1. Describe the problem your experiencing and how your idea helps solve this

The issue with this feature has been covered many times in Spectrum discussions:

Spectrum – 3 Jan 18

There is a way to avoid this by holding SPACE as soon as you click & don’t start dragging the object. But why force us to do acrobatics with our fingers by holding down an additional button, just to move the object? Why not provide an option to disable that functionality completely?

Nagaraj Chandran had a very logical idea in his comment:
“I don’t want to hold the spacebar key to disable auto-nesting. Maybe, it should be the other way around. Hold spacebar or any other key to auto-nest.”

  1. Add as much context as possible (screenshots, Figma files, mockups, etc.)

More than enough in discussions on Spectrum ☝️

  1. Ask questions to bring the community into the conversation

Does anybody find this feature useful? If yes, please enlighten me on how to make use of it because it’s driving me insane and kills my productivity big time.

68 replies

Mojo
New Participant
Mar 6, 2022 2:51 PM UTC

@Stefan_Pilipovic coyld it be you are confusing command + v with command + shift + v? I’m not getting the nested behavior you are describing, maybe I’m confused, but since I’ve discovered this shortcut is the glory

Stefan_Pilipovic
Mar 6, 2022 3:19 PM UTC

@Mojo not confusing the commands.

When using CMD+SHIFT+V it’s not auto-nesting the pasted object into the frame/group that is selected but pastes it on top of it (or above all frames if nothing is selected), positioned in the top left corner. So it solves the auto-nesting problem.

But the problem is that after that I need to move the object to the originally desired position (since it’s now pasted in the top left corner), and then re-order/move the layer in the list to put the object back in the group from which it was originally cut off. Hope this makes sense, but let me know if I’m missing anything.

IraX
Power Member
Mar 6, 2022 5:55 PM UTC

This is the exact issue I have with using shift-cmd-v for this purpose. I use shift-cmd-v a lot when needed (to literally paste over selection), but I don’t want to cut > paste > move instead of dragging.

Paul_Thackray
Mar 21, 2022 10:51 PM UTC

Agree with folks on this thread. Using Figma is like riding one of those bikes where, when you steer to the right, the front wheel steers left. It does the opposite of what I want it to, and it is causing me to lose my mind. I appreciate the collaborative nature of this product - it’s a game changer. But the UI is seriously awful.

There is literally NEVER a time where I want an object to auto-nest into a group below it. NEVER. Yet the designers at Figma decided that EVERYONE ALWAYS wants to do this. Figma has lots of serious UX issues but this one is off-the-rails bad.

mhewes
Apr 25, 2022 6:29 PM UTC

Please fix this Figma Support it really is the worst feature. It makes sense to hold SPACE to drop into a group, etc… but not as a default. It really drives me crazy on a daily basis.

nathanfrombrussels
Apr 28, 2022 7:35 AM UTC

I agree… it’s a pain in the ***, i’m struggling with this features every day of my life…

Sami2
Jul 4, 2022 10:57 AM UTC

+1
This really drives me crazy. At the very least add an option to disable auto nesting.

Jarek_Marciniak
Jul 6, 2022 6:35 AM UTC

+1 on this, guys! 😃

Keith_Rondinelli
Jul 8, 2022 8:15 PM UTC

Newly switch from Sketch and this is bonkers. Only very rarely would I ever need to auto-drop something into a frame or group. And if I wanted to do that, I’d cut-paste into the group or drag it in via layers list. This makes it almost impossible to reposition small elements without them randomly diving down into groups where they aren’t wanted!!!

Chris_Gatland
New Participant
Aug 9, 2022 10:02 AM UTC

+1000 for this issue. Coming to Figma from XD and this is driving me crazy already.

When your customer base are all UX designers, and they’re screaming at you that you have a serious UX problem, you really ought to listen to them, no?