We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Making use of the FormValidator.Tips extension to use error tips instead of the default FormValidator messages.
I'm calling validatorInstance.reset(); to clear the validation results on my form.
Problem is that calling reset() doesn't clear the pointy tip display. Is there an easy way to either:
A) Clear All Pointy Tips ?
or
B) Make reset() clear a validator instances pointy tip ?
I'm using the standard display one error tip at a time best practice.
Heres the mooshell: http://mootools.net/shell/Dt4uQ/
To reproduce:
Click form 1 email field, tab out to trigger validation tip.
Click form 2 email field. Triggers click handler to call to activationValidator.reset()
Note the css class validation-failed is removed, but the pointy tip remains.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Making use of the FormValidator.Tips extension to use error tips
instead of the default FormValidator messages.
I'm calling validatorInstance.reset(); to clear the validation results
on my form.
Problem is that calling reset() doesn't clear the pointy tip display.
Is there an easy way to either:
A) Clear All Pointy Tips ?
or
B) Make reset() clear a validator instances pointy tip ?
I'm using the standard display one error tip at a time best practice.
Heres the mooshell:
http://mootools.net/shell/Dt4uQ/
To reproduce:
Click form 1 email field, tab out to trigger validation tip.
Click form 2 email field. Triggers click handler to call to activationValidator.reset()
Note the css class validation-failed is removed, but the pointy tip remains.
The text was updated successfully, but these errors were encountered: