W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2011

[Bug 11579] The valid-email address ABNF doesn't include IDN, so for it to work the value must be punycode (or at least converted to punycode when validating), but this isn't mentioned, except as an optional example ("User agents may transform the value for display a

From: <bugzilla@jessica.w3.org>
Date: Fri, 21 Jan 2011 12:37:54 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PgGFW-00065H-6G@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11579

--- Comment #5 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-01-21 12:37:53 UTC ---
Users being unable to enter e-mail addresses with IDNs is not a UI issue at all
-- it's a functionality issue.  Saying that it's a UI issue just because they
could theoretically convert their IDN to punycode and enter it that way really
stretches the definition of "UI issue" past the breaking point, since
practically no users will know how to do that.

This does affect real-world interoperability, because it means that authors who
care about IDN support will have to work around lack of browser support in
whichever browsers don't support IDNs.  This is basically the definition of
non-interoperability.  The guideline that we don't specify UI only exists
because UI doesn't affect interoperability, so it has to be discarded when it
does (if this even is a UI issue).

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 21 January 2011 12:37:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 21 January 2011 12:38:04 GMT