Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
From w3c schools we have these definitions:
novalidate:
When present, it specifies that the form-data (input) should not be
validated when submitted.
formnovalidate:
When present, it specifies that the element should not be
validated when submitted.
Does it make any difference using formnovalidate in the submit button insted of using novalidate in the form?
(I really don’t get the difference)
novalidateis applied to the form, and prevents it from being validated;formnovalidateis applied to a submit button, and overrides thenovalidateoption, if present; it means ‘submit this form without validating, regardless of the general form setting’.The example given in the spec is when a user is saving data rather than publishing it; the data might be incomplete and invalid, but doesn’t require validation to be saved.