Reporter@ could you please provide detailed manual re-pro steps and OS & Chrome version details to triage the issue from TE end.

Thanks.

Thank you sureshkumari@ for tagging. The Blink Network team will handle it. It's direct report from the specification author.

Note: This is an element where the specification has proposed a path given UA divergence, but there's not UA consensus on the approach.

CC'ing jshin@ as well as Chrome Security team, since it's fundamentally a request to change how we process IDNs in a way that affects Chrome (and by proxy, Google), despite  (some) other UAs diverging.

Also tagging Internals>Network since this affects all Chrome //net consumers and moving to Untriaged to reflect a lack of final consensus on importance of this.

Adding back OS-IOS, because this affects //url (and thereby affects Chrome on iOS, even if not surfaced through the JavaScript URL surface). I also believe it affects the Omnibox, therefore navigation.

Chrome on iOS also depends on WebKit's JavaScript implementation (since we can't use Blink), so this behavior will not be fixed on that platform until it is fixed both for GURL and on WebKit's side.

https://bugs.webkit.org/show_bug.cgi?id=168591

Firefox and Safari (Technology Preview) have already switched. I would expect that to make it to iOS in due course.

Whoops.. didn't see that it was explicitly added again by sleevi. Will keep.

Hi Eugene: Moved back to the OS-specific labels so that TPMs have it on their radar :) I understand that some explicitly use OS-filtering labels :)