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
F18783206: D19245.id46075.diff
Mon, Oct 13, 4:47 AM
F18761704: D19245.id.diff
Mon, Oct 6, 3:49 PM
F18758999: D19245.diff
Mon, Oct 6, 1:08 AM
F18756686: D19245.diff
Sun, Oct 5, 12:44 PM
F18736138: D19245.id.diff
Wed, Oct 1, 4:58 AM
F18695529: D19245.diff
Sat, Sep 27, 5:39 AM
F18622459: D19245.diff
Sep 15 2025, 11:55 AM
F18509458: D19245.id.diff
Sep 5 2025, 3:25 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
Lint
Lint Not Applicable
Unit
Tests Not Applicable