Undo Button is Broken

Bugs
1

I have repeatedly noticed that the undo button seems to be broken.

The main issue I notice is that if I try to undo a set of changes (to check something from a prior change) and then redo all of those changes, it doesn’t redo all of the changes. It only redoes some of my original changes, so I’m left at a state that was behind where I originally was, effectively making me lose multiple steps of work that I already did.

Example:

  1. Make 10 changes
  2. Undo 10 changes
  3. Try to redo 10 changes, but you can’t redo all 10: you can only redo some of the changes you made (e.g. 5 out of the 10), therefore leaving your ending state not back where you started, costing you lost work and time.

Steps to Reproduce:

  1. Make multiple changes
  2. Undo those changes
  3. Redo all the changes
  4. Notice brokenness because state 3 is not equivalent to state 1
2

Just curious, are you on the new Beta property editor?

And I can confirm, the undo is broken

3

Not currently on the beta editor, but I suspect the issue is present on both. Haven’t yet confirmed that it is also present on the beta editor though.

I’ve been switching back and forth between them, but mostly have still been using the old/current editor, so that’s the context I’ve noticed it in.

4

I’m on the new editor so I can confirm it’s on both version

5

Are you pressing the undo button or cmd+z? Cmd+z has never been reliable since the beginning of bubble

6

Good question. Nope, just using the built-in undo button.

7
8

Yess, the undo/redo buttons can be buggy. For any larger set of changes, I prefer creating a savepoint first so I have a reliable state to restore to and another new savepoint is also created when you restore, so you can return to the state you were working from. On plans with custom branches, using a separate branch is even safer for testing bigger changes.

9

Hey Logan, thanks for the report. Like others mentioned, I think we definitely have some kind of buggy behavior that impacts undo reliability.

I flagged it to the team internally