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 7389 - Shouldn't "formnoValidate" be "formNoValidate"?
Summary: Shouldn't "formnoValidate" be "formNoValidate"?
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://whatwg.org/specs/web-apps/curr...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-20 17:20 UTC by contributor
Modified: 2010-10-04 14:30 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2009-08-20 17:20:56 UTC 
Section: http://whatwg.org/specs/web-apps/current-work/#the-button-element

Comment:
Shouldn't "formnoValidate" be "formNoValidate"?

Posted from: 216.239.45.4
Comment 1 Simon Pieters 2009-08-20 22:33:11 UTC 
You mean formNovalidate?

Not unless the novalidate attribute on HTMLFormElement is renamed to noValidate. I'm not aware of any implementations yet, so we're still free to capitalize the N in both attributes if we think it looks better.
Comment 2 Simon Pieters 2009-08-26 11:32:43 UTC 
> You mean formNovalidate?

Uh, this was me not reading the spec.


HTMLFormElement has novalidate
HTMLButtonElement has formnoValidate
HTMLInputElement has formNoValidate

I suggest to use noValidate on form and formNoValidate on button and input
Comment 3 Simon Pieters 2009-08-26 11:46:36 UTC 
(In reply to comment #1)
> I'm not aware of any implementations yet, so we're still free to
> capitalize the N in both attributes if we think it looks better.

Actually it seems Opera has implemented novalidate on HTMLFormElement and formNovalidate on HTMLButtonElement and HTMLInputElement. I'm fine with this set of names, too.
Comment 4 Ian 'Hixie' Hickson 2009-09-01 23:56:14 UTC 
Fixed to consistent casing.