We shipped a major Undo & Redo stability update for Spixor Builder

Read the Spixor post here: https://spixor.com/updates/27-builder-stability-update-a-more-reliable-undo-redo-experience

We just shipped an important stability update for the Spixor Builder.

This release focuses on something that is easy to overlook until it breaks: Undo and Redo.

In a visual builder, Undo and Redo are not just simple buttons. They sit at the center of the entire editing experience. Every text edit, settings change, style update, canvas action and internal snapshot can potentially interact with the history system.

Over the past period, we worked on improving that foundation.

The main goal was to make sure the Builder only stores real user actions in the history stack. Internal editor updates, metadata-only changes, empty snapshots and duplicate no-op changes should not become extra Undo steps. When that happens, users can experience confusing behavior, such as Redo disappearing too early or Undo stepping through changes they never intentionally made.

This update makes that behavior much more reliable.

What changed:
- Undo and Redo are more predictable after real editing actions.
- Redo is better preserved after Undo.
- Metadata-only updates are filtered instead of being stored as real edits.
- Empty or duplicate history entries are rejected more safely.
- Internal page snapshot handling has been improved.
- Settings-related changes are handled more consistently.
- The editor is better protected against late or unexpected history entries.
- Additional regression checks were added around the history system.

Why this matters:
Trust is a big part of using a visual editor. When someone edits a page, they need to know that they can safely go back, try something else, and recover their previous state. Undo and Redo are not the most visible features, but they quietly define how safe and professional the editing experience feels.

This is more of a foundation release than a shiny feature launch, but for us it is an important step. A stable history system makes every future builder improvement safer to build on top of.

Next, we are continuing the Builder stability work with a focus on canvas interactions, especially selection behavior, hover states and drag-and-drop.

Curious to hear from other makers building editors or creative tools: how do you approach Undo/Redo reliability, and how do you decide what should or should not become a history step?