Keep text typed and checkboxes or radios toggled before a form control hydrates. Hydration used to overwrite those edits with the server-rendered `value` or `checked`, so text typed into a field that streamed in with a frame was lost if its client entry hydrated a moment later. The edit is now kept and replayed as `input` and `change` events once the control's handlers are attached, so app state such as a live search query catches up with what the user sees. Replayed events are dispatched by the runtime, so `event.isTrusted` is `false`, and handlers run at hydration time rather than in response to a new user action. A handler that submits a form, saves a draft, or starts a request does so as soon as the control hydrates. Values the browser restores into a form, such as Firefox restoring fields on reload or a back/forward navigation that isn't served from the back/forward cache, count as edits too: they are now kept and replayed instead of being reset to the server-rendered values. Add `autocomplete="off"` to a control to opt it out of browser form restoration.