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 11287 - 'setCustomValidity' call in <input> element should use 'oninput' event...
Summary: 'setCustomValidity' call in <input> element should use 'oninput' event...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
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: 2010-11-10 17:40 UTC by Nick Freear
Modified: 2011-08-04 05:01 UTC (History)
4 users (show)

See Also:


Attachments

Description Nick Freear 2010-11-10 17:40:09 UTC
...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
Comment 1 Ian 'Hixie' Hickson 2010-12-29 08:39:31 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: 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.
Comment 2 Michael[tm] Smith 2011-08-04 05:01:35 UTC
mass-moved component to LC1