7389 2009-08-20 17:20:56 +0000 Shouldn't "formnoValidate" be "formNoValidate"? 2010-10-04 14:30:49 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All CLOSED FIXED http://whatwg.org/specs/web-apps/current-work/#the-button-element P3 normal LC 1 contributor ian mike public-html-admin public-html-wg-issue-tracking zcorpan public-html-bugzilla oldest_to_newest 26568 0 contributor 2009-08-20 17:20:56 +0000 Section: http://whatwg.org/specs/web-apps/current-work/#the-button-element Comment: Shouldn't "formnoValidate" be "formNoValidate"? Posted from: 216.239.45.4 26572 1 zcorpan 2009-08-20 22:33:11 +0000 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. 26688 2 zcorpan 2009-08-26 11:32:43 +0000 > 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 26689 3 zcorpan 2009-08-26 11:46:36 +0000 (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. 26789 4 ian 2009-09-01 23:56:14 +0000 Fixed to consistent casing.