-
Notifications
You must be signed in to change notification settings - Fork 137
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
IDNA2008/UTS46 #263
Comments
IDNA2008
IDNA2003
|
Both Firefox and Safari TP handle this fine: https://quuz.org/url/liveview.html#https://%E2%98%83/. ☃ is U+2603 and according to http://www.unicode.org/Public/idna/latest/IdnaMappingTable.txt that is:
So unless I'm missing in http://www.unicode.org/reports/tr46/ I'd think Python has a bug. |
I'm closing this since there's not actually an issue in either the tests or the standard and I'm not going to take responsibility for filing issues against Python. If someone wants to take that up, please! |
Hmm... please see kjd/idna#40
|
Left a comment there. |
Thanks! I wasn't really clear that uts46 and idna2008 were different from each other. |
[11:35] <noah_> hi.. i have a question about this test https://github.com/w3c/web-platform-tests/blame/e32ff14a75f30de31fb1f7ab4e7bd064dfdbfa8a/url/urltestdata.json#L4543 - i think the domain is invalid according to idna2008, so i would expect host parsing to return failure https://url.spec.whatwg.org/#host-parsing
[11:37] noah_: does UTS 46 reject it?
[11:40] <noah__> annevk: yes, at least https://pypi.python.org/pypi/idna does
[11:40] <noah__> on the other hand, maybe the whatwg spec should fall back on idna2003 if idna2008 fails, i think that might be what browsers do
[11:41] noah__: hmm, file an issue against URL? I can look next week
The text was updated successfully, but these errors were encountered: