- From: <bugzilla@jessica.w3.org>
- Date: Wed, 19 Nov 2014 18:57:14 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15489
Jungshik Shin <jshin@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jshin@chromium.org
Summary|forms: Add an attribute |forms: <input type=email>
|<input type=email idna> |validation needs to be
|that allows IDNA e-mail |updated for EAI
|addresses to be |
|round-tripped |
--- Comment #28 from Jungshik Shin <jshin@chromium.org> ---
Copying the bug report from bug 25374 and updating the summary (because EAI is
not just about IDN but also about the local part.
- 'valid e-mail address' rule doesn't support EAI [1]. [2]
- We need to avoid punycode conversion in order to support EAI. The current
<input type=email> assumes its value is always US-ASCII.
Proposal:
A) Allow EAI in type=email by default, and input.value returns user-input
string as is
B) Add new boolean attribute to enable EAI. e.g. <input type=email
internationalized>
C) Add new input type for EAI. e.g. <input type="email-i18n">
This was requested from a non-Chrome Google team.
[1] http://datatracker.ietf.org/wg/eai/
[2]
http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#valid-e-mail-address
[reply] [−] Comment 1
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 19 November 2014 18:57:17 UTC