-
Notifications
You must be signed in to change notification settings - Fork 25
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
onChange fired twice #6
Comments
Got same issue. |
Me too! :( |
Same here! |
Same issue here. |
I fixed it in the new version. |
Thanks!
…On Sat, Sep 26, 2020 at 11:30 PM oguzhanoya ***@***.***> wrote:
I fixed it in the new version.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAWMN27646UEBS5QPG2TDBDSH25XTANCNFSM4FRNKWHQ>
.
--
*Victorio Berra*
toryberra@gmail.com
636-328-7110
|
Still firing twice even when I'm using last version (1.1.3) Update: Example:
and so on ... stepDirection = none | backward | forward Dear @oguzhanoya I be more than happy to volunteer to update the documentation to provide more information, give me your approval and I'll do it :) |
For me, with the demo setup and hooking into the onChange event, the 'validate!' alert is showing 2 times when hitting next from step 2.
The text was updated successfully, but these errors were encountered: