[0.5.x] Improve native browser submission while disabling formset on submit #112
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using the Alpine library, it is common to continue using native browser form submissions.
A common pattern is to disable inputs on submit via a
fieldset
group.When we detect a native browser submission, via the
formElement.addEventListener('submit')
listener, we setprocessing = true
, however because the event listener triggers before the browser has actually sent the request it disables the inputs BEFORE the submission and the form inputs are not sent to the browser.Browsers do not submit disabled inputs.
Source: https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/disabled#usability
This PR delays setting
processing = true
until after the current tick to ensure inputs are sent before the form becomes delayed.fixes #100