OK, so a common thing, at least for me as a designer, is going back some steps, copying something and then going further to the “present” and using what I have copied.
Now I don’t know if it’s in Figma (probably yes) but just now in FigJam it turned out going back and copying resets history which is a big NO NO.
Why would copying start new history feed in the file?
Does not answer your actual question, but I ussualy bypass this by going to the file history, selecting the old version and selecting the desired element there, instead of actually using ctrl + z
Well, yeah…
and I also encountered even clicking an element is registered as “historic” : /
so if you CTRL+Z, also wondering around, viewing stuff will be actions that roll back, which is annoying if you are working, like really working on one element, and just looking around in the meantime.
Also, with going back in history, can you somehow check what was changed throughout the document, on different pages?
so if you CTRL+Z, also wondering around, viewing stuff will be actions that roll back,
I use this daily to check something, and snap back to where i was with control + z.
Also, with going back in history, can you somehow check what was changed throughout the document, on different pages?
Do you mean a side-by-side comparison? This is possible with components, but not with entire files.
Figma Learn - Help CenterNoo, just with your eye : )
After further testing, it only seems to happen if you select an item that was deleted. This does not happen in Figma. Definitely inconsistent behavior and should be reported as a bug.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.