After landing bug 1380617 nsIURI will by default return punycode .host/.hostPort/.spec Parts of the devtools that need to display the URL in a unicode format should be updated to use the nsIURI.displayHost/.displayHostPort/.displaySpec methods. In order to test this, set network.standard-url.punycode-host to true, go to a IDNA domain such as http://valentin.xn--gou-2lb.ro/ open the devtools networking panel, and see if <Request URL> and <Domain> display the correct thing. Other parts of devtools that may be affected: * Storage * Debugger * others? We should also decide _if_ we want to show unicode/punycode in the devtools. The Chrome Devtools have different behaviours for some of these fields. We should also consider adding tests for this scenario so we don't regress in the future.

Thanks for filing. Let's make this a meta bug with dependencies for each tool. (In reply to Valentin Gosu [:valentin] from comment #0) > In order to test this, set network.standard-url.punycode-host to true, go to > a IDNA domain such as http://valentin.xn--gou-2lb.ro/ open the devtools > networking panel, and see if <Request URL> and <Domain> display the correct > thing. Tested on a new profile in 57, this pref already seems to be set to true for me. Request URL and Domain both show http://valentin.xn--gou-2lb.ro/ which is good. > Other parts of devtools that may be affected: > * Storage > * Debugger > * others? The inspector and console also show URLs in their UIs. So they will be affected. > We should also decide _if_ we want to show unicode/punycode in the devtools. > The Chrome Devtools have different behaviours for some of these fields. Do you mind expanding on how does Chrome differ on this? I would tend to think that we should show punycode consistently in DevTools.