- From: <bugzilla@jessica.w3.org>
- Date: Thu, 23 Aug 2012 21:03:44 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15489 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #18 from Ian 'Hixie' Hickson <ian@hixie.ch> 2012-08-23 21:03:43 UTC --- Realistically, we can't make type=email support sending IDN to the server, because that would mean lots of people couldn't use it without first updating their entire server-side infrastructure's e-mail handling, which in some cases is impractical. Given that we're not sending IDN, it would be very strange to make it legal to receive IDN — it would mean that you couldn't round-trip all valid input data unmodified. Thus where we are now. What I expect we might do once the browsers have caught up and implemented all the new forms stuff reliably is add a new form type like "idna-email", or more likely add an attribute that can be given when type=email, which enables full IDNA in/out, not just at the UI level. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Thursday, 23 August 2012 21:03:55 UTC