W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2012

[Bug 19283] New: Investigate IDNA2003 separators

From: <bugzilla@jessica.w3.org>
Date: Fri, 05 Oct 2012 08:47:56 +0000
To: public-webapps@w3.org
Message-ID: <bug-19283-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19283

           Summary: Investigate IDNA2003 separators
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: URL
        AssignedTo: mike@w3.org
        ReportedBy: mathias@qiwi.be
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org


Continuing the discussion in https://github.com/bestiejs/punycode.js/issues/11,
I wrote a simple test that sets URLs with IDNA2003 separators U+002E, U+3002,
U+FF0E, U+FF61 as the `src` of an `iframe` element in memory, and then returns
the resulting normalized `src`.

Chrome, Safari, Firefox:

http://xn--maana-pta.com/
http://xn--maana-pta.com/
http://xn--maana-pta.com/
http://xn--maana-pta.com/

Opera:

http://mañana.com/
http://mañana.com/
http://mañana.com/
http://mañana.com/

It seems all browsers tested so far support these separators for backwards
compatibility. I haven’t tested IE yet, or older versions of the other
browsers.

-- 
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 Friday, 5 October 2012 08:47:58 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:55 GMT