-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mapDomain
doesn’t follow IDNA separator requirements
#11
Comments
I'm not entirely sure whether IDNA2008 requires this too by the way, but it seems highly unlikely browsers will ever move away from supporting these additional label separators as content relies on them working. |
Hrm, turns out IDNA2008 RFC 5895 is rather vague on this subject:
|
I think we want to have the same characters as IDNA2003, but we should prolly figure out what the browser vendors are going to implement. And then standardize that either in UTS #46 or the URL Standard. |
I have a patch ready that adds support for IDNA2003 separators. |
Committed: 131260b. Thanks again! |
As reported by @annevk,
mapDomain
does not seem to follow IDNA separator requirements.http://logbot.glob.com.au/?c=freenode%23whatwg&s=18%20Sep%202012&e=18%20Sep%202012#c722062
From http://tools.ietf.org/html/rfc3490#section-3.1 (IDNA 2003):
The text was updated successfully, but these errors were encountered: