Comment #3 on issue 30906 by wrtout: Document how chrome's IDN logic works http://code.google.com/p/chromium/issues/detail?id=30906
Folks, Chrome is doing the Punycode transformation on the IDN. However, unlike IE and FireFox: - It does not seem to be consistent in trying to resolve the DN (could be caused by pre-fetching/caching of DNS results) - Even when the resulting domain is resolvable, Chrome still displays it as Punycode (xn--abcdefgh). Both IE and FireFox will display the native IDN based on certain settings (although FF requires extra security settings, i.e. white-listing of the corresponding TLD). What are the plans for Chrome in terms of displaying the native IDN and what is the process of resolution of a given IDN? Are you folks working on this? Or is this something we can contribute to (& any direct contact info for that person/group)? Thanks in advance, -Walid -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
