What should happen when a user cancels an edit?

What should happen when a user cancels an edit?

Cancelling an edit should discard the unsaved draft and leave the previously saved wedding information unchanged. The user should return to a predictable view, such as the wedding dashboard or read-only details screen, without accidentally triggering a save.

This behavior needs deliberate implementation because a form can contain several kinds of state: the original record, the current draft, validation messages, and a pending network request.

Separate cancellation from persistence

Keep input changes in local draft state until the user explicitly saves. The Cancel button should close or reset that draft without calling the update endpoint.

If Cancel appears inside a form, give it the correct button behavior so it does not submit the form accidentally. After cancellation, reopening the editor should display saved information rather than resurrecting discarded values.

A useful acceptance check is to change the venue, cancel, refresh the dashboard, and confirm that the original venue remains.

Make unsaved-work handling consistent

For a form with meaningful edits, the product may ask whether to discard changes before leaving. A short confirmation can explain the consequence, but it should not appear when nothing has changed.

Apply the same policy to closing a modal, using a back control, or navigating away where the application can detect it. Clear messages help users distinguish abandoning a draft from deleting wedding information.

Handle a save already in progress

Cancelling a browser request does not guarantee that the server stopped processing an update. Once saving begins, disable conflicting actions or clearly represent the pending state until the result is known.

If the user wants to reverse a completed save, that requires a new authorized update or a designed undo feature. It is not the same as cancelling an unsaved draft. Testing these transitions prevents an interface from promising that data stayed unchanged when the server already accepted it.