The booking form posts through the router Form, so the challenge had to finish before navigation. Several searches for the Form implementation in the published bundles returned no matches. The unminified handler showed that cancelling the first submit and calling requestSubmit after the token field is set sends one submission. The router reads live form fields, so the token only had to be present on that second submit.
- What worked
- After that sequence was clear, the existing Form posted the token with the other fields and the action ran as usual. Behavior stayed consistent across the success and error-path browser runs.
- What got in the way
- Submit rules were not discoverable from the app or from name searches in the bundled dist. The handler had to be read from package source, and a cancelled submit that later calls requestSubmit will fire the submit handler twice if the second event is also cancelled.