docs(input[email]): note limitations with IPv6 addresses

Narretz · Narretz · commit e58b4ceed804 · 2019-01-21T20:36:46.000+01:00
Closes #16599
diff --git a/src/ng/directive/input.js b/src/ng/directive/input.js
@@ -909,8 +909,10 @@ var inputType = {
    *
    * <div class="alert alert-warning">
    * **Note:** `input[email]` uses a regex to validate email addresses that is derived from the regex
-   * used in Chromium. If you need stricter validation (e.g. requiring a top-level domain), you can
-   * use `ng-pattern` or modify the built-in validators (see the {@link guide/forms Forms guide})
+   * used in Chromium, which may not fulfill your app's requirements.
+   * If you need stricter (e.g. requiring a top-level domain), or more relaxed validation
+   * (e.g. allowing IPv6 address literals) you can use `ng-pattern` or
+   * modify the built-in validators (see the {@link guide/forms Forms guide}).
    * </div>
    *
    * @param {string} ngModel Assignable AngularJS expression to data-bind to.

Original file line number	Diff line number	Diff line change
`@@ -909,8 +909,10 @@ var inputType = {`
`909`	`909`	`*`
`910`	`910`	`* <div class="alert alert-warning">`
`911`	`911`	* Note: `input[email]` uses a regex to validate email addresses that is derived from the regex
`912`		`- * used in Chromium. If you need stricter validation (e.g. requiring a top-level domain), you can`
`913`		- * use `ng-pattern` or modify the built-in validators (see the {@link guide/forms Forms guide})
	`912`	`+ * used in Chromium, which may not fulfill your app's requirements.`
	`913`	`+ * If you need stricter (e.g. requiring a top-level domain), or more relaxed validation`
	`914`	+ * (e.g. allowing IPv6 address literals) you can use `ng-pattern` or
	`915`	`+ * modify the built-in validators (see the {@link guide/forms Forms guide}).`
`914`	`916`	`* </div>`
`915`	`917`	`*`
`916`	`918`	`* @param {string} ngModel Assignable AngularJS expression to data-bind to.`