input[email] incorrectly claims address with IPv6 address literal is invalid

[baryluk]

FYI. I am not angular user, but I found in docs, that there is a bug.

https://docs.angularjs.org/api/ng/input/input[email]

xyz@[IPv6:2001::1]

should validate as correct.

Please see https://tools.ietf.org/html/rfc5321#section-4.1.3 and section 4.1.2 and 4.1.3

[gkalpak]

Sounds accurate 😁
Thx for reporting 👍

That said, I don't think many people use "Address literals" instead of domain names and it is already possible to overwrite the email validation logic for people with more specific needs.

So, I don't think this is critical, but if someone wants to submit a pull request (in the next couple of weeks, before we enter LTS), I would be happy to review.

[baryluk]

Fully agree this is not critical and lowish priority. I do use emails with IPv6 literals sometimes tho, i.e. I have a mini monitoring system that is using email to send some notifications around, as it is workable distributed queueing (pub/sub) system, that require no additional work from me, and I want monitoring to work reliably even when DNS is down, and without access to other infrastructure (or public internet).

[Niladri24dutta]

@gkalpak Can I submit a PR for this with the updated documentation? I think only the format needs to be updated for this.

[petebacondarwin]

A docs pull request would be accepted.

[mgol]

Note that even the native <input type="email"> in Chrome doesn't recognize the provided address as valid: https://jsfiddle.net/Lnm3kj64/

[Niladri24dutta]

@mgol yes I noticed that too, so before creating the PR for this I wanted to be sure is this behavior by design for HTML5 and angular

[mgol]

I looked at the HTML spec and at the input[type="email"] section it says:

The value attribute, if specified and not empty, must have a value that is a single valid e-mail address.

The "valid e-mail address" text links to the definition of a valid e-mail address where it even (in a non-normative part) defines a JS-compatible regex for checking the value. This regex rejects IPv6 emails like the one in the original post here.

Taking that into account as well as our imminent feature freeze I think we shouldn't diverge from the standard here and just document the limitation, mentioning that native inputs behave in the same way.

As we're not going to actually fix this issue, I'm moving it to the "Won't fix" milestone. We would still accept a docs contributions explaining the situation.