This XHTML5 file serves to test how browsers implement HTML5 <input type="email"> validation, and thus how the pg_html5_email_address PostgreSQL extension should handle this validation to be in sync with both the HTML5 spec and the implementations thereof.
Apologies to the red-blue color blind (like my own brother)…
- It is obvious that an email address such as should be valid.
- But, to many people, it is less obvious that is also a valid email address.
- Pre-HTML5, when developers relied on there own guesswork to half-arse email validation rules, these rules often ended up being so strict that even an email address such as was then deemed to be incorrect. That is annoying because many people relied on, for example , to filter email from different services differently.
- And it's hard to blame them. RFC 5322 is notoriously vague and complicated. It has needless complications such as … comments: is a valid email address as per RFC 5322. The HTML5 spec disagrees. The HTML5 spec also doesn't allow spaces in the local part of an email address, such as in .
- Browser makers appear to have mixed feelings about whether unicode should be allowed in the domain name part of the email address: .
- But they seem to agree that Unicode in the local part is bad: . “We're all living in Amerika”?