Conversation
✅ Deploy Preview for mrujs canceled.
|
|
(Copying my comments from when we first chatted so they don't get lost) I thought about taking this approach as well, but it could break cases where someone has disabled the input independently. such as, a form is disabled until it is fully valid; for example: a login form that is only valid when an email & password are enabled, so the user has disabled the submit button until the form is valid. When you test this behavior with Essentially, I'm thinking about how the event doesn't trigger if a |
|
I had some time this morning and updated my reproduction of this bug to show how "re-enabling on invalid" can break the behavior of forms that independently disable submit buttons. Code: practical-computer/mrujs-constraint-validation-bug-proof-of-concept@7f03da8 In the demo, I've created a simple "toggle lock" that disables specific submit buttons. In the non-remote form, the toggle-locked button remains locked, while in the remote form it is unlocked. Demo video of "re-enabling on invalid" bug Screen.Recording.2026-01-28.at.07.25.43.movDemo video of "halt disabling if the parent form is invalid & uses constraint validation" (#220) Screen.Recording.2026-01-28.at.07.32.33.mov |
Status
Related Issue(s)
buttonelements if form is using browser validation + invalid #220We should still disable, but this re-enables if it detects an invalid event.