#17072·kit

Make `dirty` revert to false if original value is restored

Author: ciscoheatCreated Sep 9, 2026Updated Sep 9, 2026

Describe the problem

The current behavior of dirty on a remote form is, as documented, "Whether the field or any nested field has been edited since the form was mounted". When you're using it to prevent navigation with a confirm dialog, if you modify a field and then turn it back to its original value, it's still considered dirty (and hence the whole form).

This causes the confirm dialog to pop up even if there are no obvious changes.

Describe the proposed solution

Make dirty take the original state of the form into account, so if a value changes back to its original, it's not considered dirty anymore.

Alternatives considered

No response

Importance

would make my life easier

Additional Information

No response