Page MenuHomePhabricator

If a Workflow form receives a redirect response, don't re-enable the submit buttons
ClosedPublic

Authored by epriestley on Mar 21 2018, 6:46 PM.
Tags
None
Referenced Files
F13146744: D19245.diff
Fri, May 3, 10:20 AM
Unknown Object (File)
Mon, Apr 29, 2:18 AM
Unknown Object (File)
Thu, Apr 25, 3:47 AM
Unknown Object (File)
Thu, Apr 4, 11:54 PM
Unknown Object (File)
Mar 31 2024, 7:00 AM
Unknown Object (File)
Mar 31 2024, 5:39 AM
Unknown Object (File)
Mar 31 2024, 5:39 AM
Unknown Object (File)
Mar 31 2024, 5:39 AM
Subscribers
None

Details

Summary

See PHI488. Ref T13108. Currently, there is a narrow window between when the response returns and when the browser actually follows the redirect where the form is live and you can click the button again.

This is relativey easy if Phabricator is running too fast since the button may be disabled only momentarily. This seems to be easier in Firefox/Chrome than Safari.

Test Plan
  • In Firefox and Chrome, spam-clicked a comment submit button.
    • Before: could sometimes get a double-submit.
    • After: couldn't get a double-submit.
    • This could probably be reproduced more reliabily by adding a sleep(1) to whatever we're redirecting to.
  • Submitted an empty comment, got a dialog plus a still-enabled form (so this doesn't break the non-redirect case).

Diff Detail

Repository
rP Phabricator
Branch
submit1
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 19893
Build 26961: Run Core Tests
Build 26960: arc lint + arc unit