Clear signup errors while correcting fields

User intention

Help me correct my email address and password on the signup form.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both
BeforeThe defect at the parent commit
0:00.00 / 0:00.00Frame 0 · Replace short in Password with Kestrel!482

Watch the password correction and compare the entered value with its minimum-length validation message.

AfterThe same script once the merged fix is applied
0:00.00 / 0:00.00Frame 0

Correct the email and password in turn and inspect the validation feedback beside each field.

How is it judged?

01 · Given
Restore the data and starting state.
On the signup form, before submission, Full Name is Alex Morgan, Email Address is alex, and the revealed Password is short. Email Address and Password have both been blurred and show their respective invalid-email and minimum-eight-character errors.

02 · When
Perform the interaction.
Append @example.com to Email Address while it retains focus, then move focus to Password and replace short with Kestrel!482 while retaining focus in Password. Do not submit the form.

03 · Judge
Rationale: Signup users need to know whether correcting their credentials worked. An obsolete error makes a valid value appear invalid and obstructs recovery even though the input now satisfies the rules.
Require
After an email or password has shown a validation error, valid correction must promptly clear that error and its invalid styling while the field remains focused, without blur or submission. Invalid values must retain accurate validation feedback.
Allowed
  • Revalidation may occur during input or after a short typing pause, provided feedback updates without a focus change or submission.
  • Success feedback may be omitted or shown in any readable form; exact wording, colors, layout, and the validation library are unrestricted.
  • Initial validation may wait until blur; this case requires timely revalidation of errors already shown, not an error on the first keystroke.

Who repaired it