[Webkit-unassigned] [Bug 48491] New: using setCustomValidity makes checkValidity unreliable

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Oct 27 18:59:34 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=48491

           Summary: using setCustomValidity makes checkValidity unreliable
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh
               URL: http://afarkas.github.com/webshim/tests/safari.html
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Forms
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: info at corrupt-system.de


This bug is extremly curious. After setting setCustomValidity('error') on an element with a constrain (i.e.: required). The checkValidity method return false, if the field is not empty and the setCustomValidity was set to an empty string. The validityState returns true for the valid-flag. You will find a testcase @ http://afarkas.github.com/webshim/tests/safari.html. (Hope this makes it much clearer). This bug should have a high priority and should block bug 28649.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list