Bug 48491 - using setCustomValidity makes checkValidity unreliable
Summary: using setCustomValidity makes checkValidity unreliable
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac All
: P2 Normal
Assignee: Nobody
URL: http://afarkas.github.com/webshim/tes...
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-27 18:59 PDT by alexander farkas
Modified: 2010-10-27 23:10 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description alexander farkas 2010-10-27 18:59:34 PDT 
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.
Comment 1 Kent Tamura 2010-10-27 23:10:09 PDT 
I confirmed that Safari 5.0.2 had this problem.  However Safari nightly with today's WebKit and Google Chrome 8.0.552.18 doesn't have the problem.  I'm not sure what revision fixed the problem.