aFarkas/webshim — Issue #90: not getting expected results from checkValidity()
Author: btaitelb
Created: 2012-01-18 21:12:13+00:00
State: open

I created some failing QUnit tests to demonstrate what I'm seeing: https://gist.github.com/1635665

It's very likely that I'm doing something wrong, but I can't figure out how these tests differ from the checkValidity tests in validate.js

Some notes:

- if you uncomment the calls to prop('validity').valid not only do those lines pass, but then the subsequent calls to checkValidity will return the correct result
- I included the test for maxlength, because it's not showing me the desired results, although according to http://www.w3.org/TR/html5/association-of-controls-and-forms.html#limiting-user-input-length it seems that a browser only needs to validate the maxlength if the value is changed by a user, not a script. This test passes in Safari, but fails in ff9 and chrome.