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
Overview
My take on why it should be avoided
Note: You can set novalidate to disable native validation and display your own custom validation messages by checking the status of the validity of each field. However, that only addresses my first point on the tweet above.
novalidate
Other reasons to avoid, mentioned in the thread above:
Three key pieces to built-in form validation:
The tradeoff: Built-in validation isn't as customizable as JS validation. And, it looks different across browser, which cannot be resolved.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Overview
My take on why it should be avoided
Note: You can set
novalidate
to disable native validation and display your own custom validation messages by checking the status of the validity of each field. However, that only addresses my first point on the tweet above.Other reasons to avoid, mentioned in the thread above:
Three key pieces to built-in form validation:
The tradeoff: Built-in validation isn't as customizable as JS validation. And, it looks different across browser, which cannot be resolved.
The text was updated successfully, but these errors were encountered: