In your experience, how often is the undo/redo button buggy?

[randomanon]

Let me know your experiences with this below!

• Always
• Often
• Sometimes
• Rarely
• Never

[manipaje]

I just wish it could say ‘what’ it will undo / redo. The click and hope nature of it sucks sometimes.

[randomanon]

Yep, you can lose hours of work. It needs to be the most rock-solid feature, yet is the least stable and trustworthy. And they are going to build an AI agent on top of it?

[boston85719]

@randomanon

Yep, you can lose hours of work

With that statement seems you’re using the feature wrong and don’t know its limits…it’s 50 steps, that’s it. If you take less than 50 steps in hours of working you’re doing something seriously wrong.

50 steps, a dynamic expression of current user is logged in and current user role is admin takes about 8 steps to craft.

You might want to explore how to use save points if undo button causes you to lose hours of working.

Lose hours of work

[randomanon]

@boston85719

it’s 50 steps, that’s it

It’s less if you perform any actions that bug the undo/redo feature in the middle of actions that (usually) don’t. For example, you added a text element, then changed a transition or style, then added a group element. If you undo past the transition then try to redo, it will lose everything up to that point.

@boston85719

You might want to explore how to use save points

Oh trust me, that’s pretty much all I use these days. Doesn’t feel good using a 1990’s workflow where I have to constantly manually save because a critical fundamental feature doesn’t work.

[emir.ozgun]

@randomanon

you added a text element, then changed a transition or style, then added a group element. If you undo past the transition then try to redo, it will lose everything up to that point.

Can you elaborate more on this?

[randomanon]

Sure. So, there are certain things you can do in Bubble that will break the undo/redo button 100% of the time. A couple of these off the top of my head are changing transitions (e.g., 300 ms Opacity Ease-In-Out –> 250 ms Opacity Ease-In) and styles (detach style, etc.)¹. There are other actions that have a high probability (but not 100%) of breaking the undo/redo button. These include things like collapsing groups. Then there are “normal” actions that rarely break the undo/redo button (e.g., min height 40 –> 100).

If you include breaking actions in a chain of “normal” actions, the entire chain becomes corrupted.

¹It’s interesting seeing the votes for the “Never” category, because it means these users literally don’t use certain features in Bubble.

[boston85719]

@randomanon

¹It’s interesting seeing the votes for the “Never” category, because it means these users literally don’t use certain features in Bubble.

IDK if 612 times is not using something

[emir.ozgun]

Never experienced min height thing, detach style I remember something like when undoing, style overridden stays?. Will try transition thing, overall transitions are not reliable so I dont use them.

[fede.bubble]

@randomanon

¹It’s interesting seeing the votes for the “Never” category, because it means these users literally don’t use certain features in Bubble.

Tossing out results you don’t agree with means you had already decided what the correct outcome was before launching the poll. So what’s the point of doing it?
Edit: voted always so you get a full range

[randomanon]

@boston85719

IDK if 612 times is not using something

I meant transitions. If undo/redo has never failed for you, it means you’ve never used a transition.

@fede.bubble

Tossing out results you don’t agree with

Not sure why you think I’m “tossing them out.” If I wanted to skew the results I wouldn’t allow that option. Note that “Never” represents an small minority.

@fede.bubble

So what’s the point of doing it?

To collect a representative dataset of engaged users’ experiences with the undo/redo button. I would hope this would reach the team.