Skip to content
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

URL: Update IdnaTestV2 to UTS46 16.0.0 #48301

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

rmisev
Copy link
Member

@rmisev rmisev commented Sep 21, 2024

Updates IdnaTestV2-parser.py for version 16.0.0 of Unicode IDNA Compatibility Processing [UTS46] and fixes other issues:

  • Adds the encoding="utf-8" parameter to file open calls to run correctly if the default system encoding is not utf-8
  • Fixes the parameter that is written to the output file: --exclude_bidi changed to --exclude-bidi

@@ -92,13 +96,11 @@ def parse(lines, exclude_ipv4_like, exclude_std3, exclude_bidi):
continue

if exclude_std3:
if re.search(r"\u2260|\u226E|\u226F|\<|\>|\$|,", to_unicode):
if re.search(r"\<|\>|\$|\?|,", to_unicode):
Copy link
Member Author

@rmisev rmisev Sep 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • I removed \u2260, \u226E and \u226F. because they are labeled valid starting with UTS46 15.1.0.
  • I added ? because IdnaTestV2.txt contains tests with it and it is the forbidden domain code point.
  • I am not sure if $ and , are still needed here?

@annevk
Copy link
Member

annevk commented Sep 23, 2024

Thank you for working on this, but I'm not sure this can be merged as-is.

This results in failures for both Firefox and Safari, both thought to have compliant implementations. I'm not sure I fully trust the updated tests. Especially given that we still have some open issues against the URL Standard about sorting out some IDNA issues with UTS 46.

Did you investigate the failures?

@rmisev
Copy link
Member Author

rmisev commented Sep 23, 2024

I think it's normal that about 70 tests fail with Firefox and Safari. About the same number of tests failed when I tested with my UTS46 15.1.0 implementation. There are no failed tests on my UTS46 16.0.0 implementation. I think there may be similar results with browsers when they switch to UTS46 16.0.0

@annevk
Copy link
Member

annevk commented Sep 23, 2024

That's fair, I guess the problem is that I'm not entirely convinced that the UTS 46 update is fault-free given the response we've been given to some of the issues we've raised.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants