- From: <bugzilla@jessica.w3.org>
- Date: Wed, 30 Mar 2016 08:06:34 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15489 Kent Tamura <tkent@chromium.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tkent@chromium.or | |g) | --- Comment #37 from Kent Tamura <tkent@chromium.org> --- (In reply to Anne from comment #34) > So I think the best solution here is simply change the definition of what > constitutes a "valid e-mail address". > > This is a little bit backwards incompatible, but given that servers will > already have to validate what ends up being submitted I don't think it will > actually be a problem, especially since EAI is a strict superset. I prefer adding a content attribute or an input type for EAI. I don't want to ship such incompatible change. Many systems aren't ready for EAI, and rejecting EAI on client-side would have better UX than rejecting EAI on server-side. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 30 March 2016 08:06:39 UTC