Skip to content

Commit

Permalink
Fixed type in docs.
Browse files Browse the repository at this point in the history
  • Loading branch information
Eric Hamilton committed Nov 14, 2011
1 parent 338b0a3 commit 2d3e507
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion index.html
Expand Up @@ -119,7 +119,7 @@ <h2>New Input Types (Use with caution.)</h2>
<p>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 <code>-webkit-appearance: searchfield;</code> 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.</p>
</div>

<p>h5Validate does not currently validate new element types automatically. The <code>pattern</code> and <code>required</code> attributes work fine, but h5Validate <strong>will not</strong> automatically apply email validation to fields with <code>type="input"</code>. (Yet...)</p>
<p>h5Validate does not currently validate new element types automatically. The <code>pattern</code> and <code>required</code> attributes work fine, but h5Validate <strong>will not</strong> automatically apply email validation to fields with <code>type="email"</code>. (Yet...)</p>

<p>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.</p>

Expand Down
2 changes: 1 addition & 1 deletion 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
Expand Down

0 comments on commit 2d3e507

Please sign in to comment.