forms with `data-remote` + `data-disable` that use constraint validation are locked out when browser's "submit by pressing enter" behavior is used

[tcannonfodder]

I have a reproduction repo here: https://github.com/practical-computer/mrujs-constraint-validation-bug-proof-of-concept

Expected Behaviour

• Similar to the normal browser behavior, when a form is attempted to be submitted, the button is not disabled if the form is invalid

Actual Behaviour

• If the form is invalid according to the Constraint Validation API, the submit button is disabled and cannot be re-enabled.

Steps to Reproduce

See repo above for a focused, streamlined example

I'm actively debugging how to best solve this, but wanted to raise it

[tcannonfodder]

Potential fixes:

• Removing the disable event handler on click, only trigger it when a submit actually occurs
• Only continuing the disable event handler if form.checkValidity is true?

[tcannonfodder]

Potential fixes:
[...]

• Only continuing the disable event handler if form.checkValidity is true?

Going to work on a PR with this fix, since it feels like the most appropriate solution. Mrujs should not try to submit a form if the browser has determined that it is invalid according to its internal Constraint Validation API. If folks want to circumvent the Constraint Validation API, they can use novalidate