This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11060 - I see a good description for formnovalidate, but not for novalidate. I assume that novalidate exempts an individual input from validation, whereas formnovalidate is used on buttons and applies to the whole form. Is that a correct reading? This should be m
Summary: I see a good description for formnovalidate, but not for novalidate. I assume...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-15 03:29 UTC by contributor
Modified: 2011-08-04 05:16 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-10-15 03:29:12 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#attr-fs-novalidate

Comment:
I see a good description for formnovalidate, but not for novalidate. I assume
that novalidate exempts an individual input from validation, whereas
formnovalidate is used on buttons and applies to the whole form. Is that a
correct reading? This should be more clear.

Posted from: 174.61.12.85
Comment 1 Tab Atkins Jr. 2010-10-15 15:38:04 UTC 
The information you need is specified right below the subheading of the section you've referenced.

"The attributes for form submission that may be specified on form elements are action, enctype, method, novalidate, and target."

@novalidate is placed on <form> and turns off validation for the whole thing.
Comment 2 Ian 'Hixie' Hickson 2010-12-26 20:11:51 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: The two attributes seem to be defined in exactly the same way in the same paragraph. Why is formnovalidate clear but novalidate not? What would help clarify it?
Comment 3 Michael[tm] Smith 2011-08-04 05:16:54 UTC 
mass-move component to LC1