What's worse, some of the styles that get applied to these elements are browser-specific, and ignore CSS cascading -- so before you can add your own look and feel, you first have to turn off each native browser's look and feel. For example, h5Validate works just fine on that search field down there, but in Chrome, it ignores our CSS because you first have to turn off -webkit-appearance: searchfield; before you style it. (Hint: You may want to search for a good HTML5 CSS reset). I've left it as is to demonstrate how irritating all of this can be. Good luck, and don't say I didn't warn you.
h5Validate does not currently validate new element types automatically. The pattern and required attributes work fine, but h5Validate will not automatically apply email validation to fields with type="input". (Yet...)
h5Validate does not currently validate new element types automatically. The pattern and required attributes work fine, but h5Validate will not automatically apply email validation to fields with type="email". (Yet...)
The plan is to create a thorough testsuite to make sure these validations comply with the html5 standard prior to implementation. So far, it looks like some of the browser implementations are inconsistent. We'll be sharing test cases and filing bug reports in an effort to get all of these validations behaving the same way. Any help with the effort is appreciated. In particular, test cases that show how various implementations differ from the spec would be great. Eventually, we'll defer to the native browser implementation if it's available, with a fall-back to h5Validate's built-in validation rules.
diff --git a/jquery.h5validate.js b/jquery.h5validate.js index 7fbdaa1..bcfe8e9 100755 --- a/jquery.h5validate.js +++ b/jquery.h5validate.js @@ -1,6 +1,6 @@ /** * h5Validate - * @version v0.6.2 + * @version v0.6.3 * Using semantic versioning: http://semver.org/ * @author Eric Hamilton dilvie@dilvie.com * @copyright 2010 - 2011 Eric Hamilton