Show report validation and focus the description

User intention

Submit a website issue report as a guest.

Report a missing image in the lesson I am taking.

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

Submitting the blank website report leaves the lower form in view; scrolling upward reveals the description warning.

AfterThe same script once the merged fix is applied

0:00.00 / 0:00.00Frame 0

Submitting the blank website report brings the description and its warning into view.

How is it judged?

01 · Given

Restore the data and starting state.

A guest has opened Report a Website Issue from the home-page footer. Describe the issue is empty, and the dialog's form body is scrolled down so screenshot and technical-log controls are visible while the description is above the visible area. Submit remains available.

02 · When

Perform the interaction.

Click Submit without entering a description.

03 · Judge

Rationale: A missing-description warning outside the scrolled viewport leaves Submit's failure unexplained. Making the reason and correction reachable lets the user finish the report without losing other input.

Require

On rejecting the empty report, immediately show that a description is required and provide a direct way to correct it without searching by scrolling. Keep the report open and preserve existing optional inputs.

Allowed

Automatically reveal the description and its inline warning by scrolling or focusing the field.
A visible validation summary or message at the current position is acceptable if it identifies the missing description and provides a direct way to reach the field.
Error wording and styling may vary if the cause and corrective action are clear.