436597edef Core: Validate inputs with duplicate name / name[] arrays, instead of just the first item (#2498)
* Allow input name arrays

* Allow input name arrays

* Core: Fix checkbox name cache and add name[] tests

Use the DOM element's name so each checkbox/radio group is cached
separately, keep groups first-only in elements(), and cover name[]
plus duplicate-name text inputs.

* Core: wip

* Core: wip

* Core: Pick the plain-name owner from the elements that get validated

uniqueName() handed the plain name to the first element of that name
after only the ignore filter, so a disabled, submit/reset/image or
rule-less element in front of the one field elements() validates
pushed that field to "name-2". errorMap keys, the invalid map and the
error label of an id-less field then no longer matched the plain name
they had before. Use the same filter as elements() when choosing the
first element.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* Core: Keep a checkbox/radio group's name exclusive to the group

elements() only skipped later checkables of an already seen name, so a
text or hidden input following a checkbox/radio group of the same name
was validated with the group's name-keyed rules, and could fail them in
ways the user cannot fix (e.g. a hidden companion with ignore: []).
Record whether a name was claimed by a checkable and skip every other
element of that name, as before this branch. Such companions also keep
sharing the group's plain key in uniqueName().

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* Core: Stop remote() polluting Object.prototype via the message stash

For an input named "__proto__" (or "constructor"), settings.messages[
key ] resolves to an inherited member, so stashing the remote message
on it wrote Object.prototype.remote and broke validation page-wide.
Only write to an own entry of the messages map, creating it with
Object.defineProperty where needed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

---------

Co-authored-by: bytestream <kieran@supportpal.com>
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-26 14:39:21 +00:00
2026-06-01 11:19:52 +01:00
2026-06-01 11:19:52 +01:00
2026-01-22 15:36:46 +00:00
2026-01-22 15:36:46 +00:00
2017-04-08 00:35:14 +01:00
2026-06-01 11:19:52 +01:00
2021-09-12 08:45:02 +02:00

jQuery Validation Plugin - Form validation made easy

release Build Status devDependency Status jsDelivr Hits

The jQuery Validation Plugin provides drop-in validation for your existing forms, while making all kinds of customizations to fit your application really easy.

Getting Started

Downloading the prebuilt files

Prebuilt files can be downloaded from https://jqueryvalidation.org/

Downloading the latest changes

The unreleased development files can be obtained by:

  1. Downloading or Forking this repository
  2. Setup the build
  3. Run grunt to create the built files in the "dist" directory

Including it on your page

Include jQuery and the plugin on a page. Then select a form to validate and call the validate method.

<form>
	<input required>
</form>
<script src="jquery.js"></script>
<script src="jquery.validate.js"></script>
<script>
    $("form").validate();
</script>

Alternatively include jQuery and the plugin via requirejs in your module.

define(["jquery", "jquery.validate"], function( $ ) {
	$("form").validate();
});

For more information on how to setup a rules and customizations, check the documentation.

Reporting issues and contributing code

See the Contributing Guidelines for details.

IMPORTANT NOTE ABOUT EMAIL VALIDATION. As of version 1.12.0 this plugin is using the same regular expression that the HTML5 specification suggests for browsers to use. We will follow their lead and use the same check. If you think the specification is wrong, please report the issue to them. If you have different requirements, consider using a custom method. In case you need to adjust the built-in validation regular expression patterns, please follow the documentation.

IMPORTANT NOTE ABOUT REQUIRED METHOD. As of version 1.14.0 this plugin stops trimming white spaces from the value of the attached element. If you want to achieve the same result, you can use the normalizer that can be used to transform the value of an element before validation. This feature was available since v1.15.0. In other words, you can do something like this:

$("#myForm").validate({
	rules: {
		username: {
			required: true,
			// Using the normalizer to trim the value of the element
			// before validating it.
			//
			// The value of `this` inside the `normalizer` is the corresponding
			// DOMElement. In this example, `this` references the `username` element.
			normalizer: function(value) {
				return $.trim(value);
			}
		}
	}
});

Accessibility

For an invalid field, the default output for the jQuery Validation Plugin is an error message in a <label> element. This results in two <label> elements pointing to a single input field using the for attribute. While this is valid HTML, it has inconsistent support across screen readers.

For greater screen reader support in your form's validation, use the errorElement parameter in the validate() method. This option outputs the error in an element of your choice and automatically adds ARIA attributes to the HTML that help with screen reader support.

aria-describedby is added to the input field and it is programmatically tied to the error element chosen in the errorElement parameter.

$("#myform").validate({
  errorElement: "span"
});
<label for="name">Name</label>
<input id="name" aria-describedby="unique-id-here">
<span class="error" id="unique-id-here">This field is required</span>

Learn more about errorElement

License

Copyright © Jörn Zaefferer
Licensed under the MIT license.

Languages
JavaScript 95%
HTML 5%