W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2010

[Bug 11287] New: 'setCustomValidity' call in <input> element should use 'oninput' event...

From: <bugzilla@jessica.w3.org>
Date: Wed, 10 Nov 2010 17:40:09 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-11287-2486@http.www.w3.org/Bugs/Public/>

           Summary: 'setCustomValidity' call in <input> element should use
                    'oninput' event...
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: n.d.freear+w3bugs@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,

...not the 'onforminput' event - I think.

This concerns the HTML snippet under section, The required attribute
at both these URLs:

<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,

I hope that helps. Keep up the great work!



Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 10 November 2010 17:40:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:33 UTC