Frontend & browser·State, data and re-rendering
you track whether the form has been touched so you can warn before the user navigates away.
Dirty state
Also calledunsaved changes, dirty form
A flag recording that local edits have not yet been persisted. It drives the unsaved-changes prompt, the enabled state of a save button, and whether a background revalidation is allowed to overwrite what is on screen. That last one is the subtle part: a refetch that clobbers a half-written form is a data-loss bug, not a caching detail.