11287 2010-11-10 17:40:09 +0000 'setCustomValidity' call in <input> element should use 'oninput' event... 2011-08-04 05:01:35 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED WONTFIX http://whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#attr-input-required P2 normal --- 1 n.d.freear+w3bugs ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 42383 0 n.d.freear+w3bugs 2010-11-10 17:40:09 +0000 ...not the 'onforminput' event - I think. This concerns the HTML snippet under section 4.10.7.2.5, The required attribute at both these URLs: * http://whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#attr-input-required * http://w3.org/TR/html5/common-input-element-attributes.html#the-required-attribute <input id="password2" type=password onforminput="setCustomValidity(value != password1.value ? 'Passwords do not match.' : '')"> I can get oninput="setCustomValidity..." to work in Firefox 4 Beta 6 (Windows), but not onforminput="...". You may wish to compare with this example, * http://w3.org/TR/html5/association-of-controls-and-forms.html#dom-cva-setcustomvalidity I hope that helps. Keep up the great work! Cheers, Nick 43621 1 ian 2010-12-29 08:39:31 +0000 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: Rejected Change Description: no spec change Rationale: Sounds like FF just doesn't support onforminput yet. Using onforminput in this example is intentional, since otherwise the form control's validity wouldn't update when the user changes the _other_ input control. 52448 2 mike 2011-08-04 05:01:35 +0000 mass-moved component to LC1