Skip to main content
Stefan_Pilipovic
February 11, 2021

Disable auto-nesting/auto-reparenting while moving objects

  • February 11, 2021
  • 68 replies
  • 17236 views
  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

Tom_Auger1
New Participant
July 21, 2023

I think what’s really sad with Figma (and many other software companies, TBH) is that their QA, dev or customer success teams never comb the forums. They put these forums up for the community to “support each other” so they don’t have to, but there are real nuggets (like this one) that have a ton of responses over 3 YEARS that hasn’t even been graced with a single official response from the Figma team. I can only expect this to get WORSE with the recent Adobe acquisition (if Figma even survives it).

Prove me wrong, Figma. Respond to this thread and tell us someone is listening and cares.

James_Walsh
New Participant
July 24, 2023

This still annoys me on a day to day basis. Would it be so difficult to allow a user preference for this? Holding space is such an annoyance (especially when there is no visual confirmation you pressed it at just the right time. I’d even accept a plus on the grabbed hand cursor or something?)

Keith_Rondinelli
September 25, 2023

Any solutions for this on the horizon? This is just a terribly annoying “feature” in Figma. I find I can’t reposition an item without it popping down into a group / frame where I don’t want it, or out of the main frame altogether. There should simply be a user preference, checked on or off, that says, “disable auto-nesting of dragged objects” and be done with it.

Kristen_Abercrombie
October 12, 2023

This has been driving me bonkers lately, it’s alway been an annoyance but it feels like it’s gotten worse, if that’s possible? It’s like it got more sensitive, layers are auto-nesting into frames that I’ve barely dragged over. Weird. I love Figma, but this particular thing is so frustrating and slows me down.

November 1, 2023

this is the most idiotic thing ever. it makes me a lot less productive, because I’m always trying to remember to hold spacebar and sometimes it just auto-nest anyways.

Basilicom
New Member
November 2, 2023

full support on inverting this “feature”. Its so damn annoying.

mr.D
November 2, 2023

Introducing a universal setting to turn off this feature should satisfy all users. If you’re reading this and haven’t yet given it an upvote or left a comment, please consider doing so to help amplify our message.

Luciano_Foglia
December 3, 2023

Please disable or make it an option. It’s counter intuitive to use. Thanks

JPress
New Participant
January 19, 2024

I’m in complete agreement with all of this. I can’t understand why this is the default functionality. Even when a frame is behind other layers, it still tries to nest what you’re dragging into the frame, regardless of how many other layers/objects are in front.

Here’s a recording of this happening. I’m trying to duplicate the objects, and the frame the objects are being forced into is several layers behind. I don’t see what the logic to this behavior is, certainly not on default.

JPress
New Participant
February 23, 2024

Just want to bump this so it doesn’t get closed for inactivity. Please take a serious look at this. It’s a major disruption to working efficiently.