Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

auro-form event listeners are brittle when setting disabled states on form controls #318

Open
DukeFerdinand opened this issue Feb 11, 2025 · 1 comment · Fixed by #319
Open
Assignees

Comments

@DukeFerdinand
Copy link

Please verify the version of auro-form you have installed

1.5.0

Please describe the bug

This is fixed, just capturing work done.

Form events don't always trigger in the expected validated, input, (update) order, leading to issues where the state is 100% valid, but the form is not aware of its own validity and therefore does not update button states to match expectations.

Reproducing the error

None

Expected behavior

No response

What browsers are you seeing the problem on?

No response

Additional context

No response

Exit criteria

No response

@jason-capsule42
Copy link
Member

🎉 This issue has been resolved in version 2.0.0-beta.41 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants