Which form input validation method is sometimes referred to as pogo-sticking?

Which form input validation method is sometimes referred to as pogo-sticking?

• A. Requiring users to click Submit before validation occurs
• B. Live validation on every keystroke
• C. Validation after form submission
• D. External validation

Answer: (A)

Pogo-sticking happens when validation forces a back-and-forth ride between pages: you fill out a form, submit it, the server checks the data and returns you to the same form page with error messages, you fix what’s wrong, and submit again. That round trip—form page to results back to the form—feels like bouncing between pages, hence the term. Requiring users to click Submit before validation occurs fits this pattern exactly, because validation is triggered only after submission and the page reloads to show errors, creating that disruptive back-and-forth flow. In contrast, validating on each keystroke stays on the same page and gives immediate feedback without navigation, so it avoids pogo-sticking. Validation after submission is the same cycle described above, and external validation isn’t inherently tied to this back-and-forth page behavior.

Pogo-sticking happens when validation forces a back-and-forth ride between pages: you fill out a form, submit it, the server checks the data and returns you to the same form page with error messages, you fix what’s wrong, and submit again. That round trip—form page to results back to the form—feels like bouncing between pages, hence the term. Requiring users to click Submit before validation occurs fits this pattern exactly, because validation is triggered only after submission and the page reloads to show errors, creating that disruptive back-and-forth flow.

In contrast, validating on each keystroke stays on the same page and gives immediate feedback without navigation, so it avoids pogo-sticking. Validation after submission is the same cycle described above, and external validation isn’t inherently tied to this back-and-forth page behavior.