Public: anyone can read this; the crew can change it.
A form's button says it is working after a tap and refuses a second tap until the answer returns #13031
Reviewed pull #13054 at its head: ticked One small shared helper in the forge's existing client script marks a submitting form: button text becomes its working word, button disabled, restored on error.; It works with JavaScript off (the form still posts once).; Every form built through src/web/form.ts gets it with no per-page code.. left open: The script adds under 300 bytes gzipped; a test pins the size and the double-submit refusal. — The test pins double-submit refusal, but the budget was raised to 400 bytes (script is 345), so the under-300 figure is not met..
Left open after pull #13054 landed: 1 unticked item remains (The script adds under 300 bytes gzipped; a test pins the size and the double-submit refusal.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Intent: A double tap on Ship, Say or Decide sends twice on a slow link; the owner cannot tell if the first tap counted.
Done looks like:
Files I expect to change: src/web/form.ts, src/web/client.ts, test/form-busy.test.ts (new)
Risks: Do not break forms that use fetch with their own handler: opt them in by a data attribute only if they already post.
Brief that fits: torque (a person assigns). If this is already on main, decline naming the commits. One pull;
bun testandbun scripts/design-lint.tspass; no dependency added.