When I undo, I want undo only changes that I’ve made to a document, not what I’ve selected. I find the existing behavior to be unintuitive and counter to basically all other applications.
However, I realize some people like it the way it is, so we can we get a user option to only include document changes in Undo?
When I undo in Figma (history), it goes the whole way back though all the selections and edits, while I’ve never seen any app that considers selections as edits. This feels odd, and it takes much more time to actually undo real edits.
I’d recommend to apply undo only to actions such as “text edit”, “delete”, “move”, “group”, “create”, “color change”, “paste”, etc. But not to simple layer selection.
Agreed, it makes undo incredibly frustrating, and means i have to hit undo an unreasonable amount of times, especially if i am selecting my way into a nested autolayout. i just had to hit undo 8 times to undo an action i did to a complex component because i needed to select thru 7 nested autolayouts in order to get to the last action i just did. SELECTION IS NOT AN ACTION
Please add this option! It adds 2x clicks/actions to my stack every day, all day.
I really want this.
Both methods have their own advantages.
Personally, the current way makes too many small mistakes. So painful.
I am frustrated with Figma right now. I want to undo a last action of resizing something however ctrl + z doesn’t seem to be working the same way as before. I can’t now see what undo’s I am doing based on this. I just want to be able to work the way I used to before. So it should be a preference thing not just a change Figma thinks will make everyones workflow better.
It is definitely very annoying and frustrating to be “undoing” clicks. If this is a loved behavior, at least please let us set a preference so that item selections are not considered undoable / redoable actions.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
I was asked why I prefer to have selection included in the undo history. Here are my reasons:
If you click in the wrong spot while doing a complex multi-layer selection, you don’t need to start over in Figma (drives me insane in other apps).
Moving around the pages and canvas selecting different frames, then being able to easily go back if necessary.
So both of these are obviously about selection/navigation. They are not really a part of a regular undo flow.
This suggestion therefore is not really about “we need an option for that” but more about “let’s get rid of this feature but keep it as an option in case someone wants it”.
With these things in mind, I believe there is an opportunity to kill two birds with one stone. A popular suggestion on the forum is Quickly go to last visited page and back. It’s pretty much what I currently use Undo history for sometimes.
So I’m thinking: why not combine selection/navigation history into one thread and separate it from the undo history? This way workflows I described would still be available at all times without the need to enable/disable any options. And navigation wouldn’t disrupt the undo history. The navigation/selection back/forward actions should obviously be available with shortcuts and probably with the UI buttons too.
This issue is singularly so annoying and bizarre that I am in the process of switching away from Figma.
Was this ever implemented in Figma? This is one of the major reasons that keeps my team from moving to Figma since the current way (including layer/object selections in undo) makes the application too difficult to work in.
Is there a way we can manually turn off selections as edits while undoing?
I just starting using Figma a few days ago, and this is one thing I found super frustrating. I found my self undoing multiple times because of selections. Specially in prototyping, when the majority of my selections was to view interactions, and having to undo about a dozen times just to undo one actual edit. It would be great if we had an option to not include selections in undo.
This reminds me of when Adobe changed the Free-Transform a few years back, where you didn’t have to use Shift to constraint proportions (trying to use mobile patterns in desktop). What a mess it was until they finally gave users the option to use it how it had always been.