342605 - IDN URLs in console output are mangled

Status: RESOLVED INVALID

(DevTools :: Console, defect, P3)

Description

[Jungshik Shin]

This bug report is in UTF-8. (please, add your comments after setting View | Char. encoding to UTF-8)

IDN in error console is mangled because an IDN in UTF-8 passed to the error console is treated as if it's is ISO-8859-1 (that is, each byte is zero-padded to turn it to UTF-16). 

How to reproduce:
  Go to the url above in the url box above (http://www.청와대.gov) and open up the error console to find a gibberish in the domain name part instead of 'http://www.청와대.gov'. Also click on one of gibberish urls and naturally, you'll get a 'host not found' error.

Comment 1

[Simon Bünzli]

This seems rather to be an issue with the components which report the errors than with how the Error Console displays them:

Warning: Unknown property 'list-type'.  Declaration dropped.
Source file: http://www.ì²­ìë.kr/cwd/kr/include/new/css/main.css
Line: 89
 ----------
Warning: Element referenced by ID/NAME in the global scope. Use W3C standard document.getElementById() instead.
Source file: http://www.청와대.kr/cwd/kr/opensite/popup/new_multi5.php
Line: 156

Comment 2

[Alexis Lecocq]

This bug is still present in Firefox 42.0 and is very frustrating when debugging IDN websites. JS errors are reported with a wrong domain. When you click on the error to see the error line, the source displayed is fetched from an other (wrong) domain.

Old URLs seem down so I made some new URLs for you to reproduce :
- Go to https://ç.co/js-error.php ( you can view source to get the right ASCII domain view-source:https://xn--7ca.co/js-error.php )
- Open developer console and click on the JS error, you will be redirected to view-source:https://xn--eba3j.co/js-error.php which is a wrong domain

If you need any additional informations, feel free to ask.

Comment 3

[Brian Grinstead [:bgrins]]

The Error Console has been removed in favor of the Browser Console (see Bug 1278368), and the component is going to be removed.  If this bug is also relevant in the Browser Console, please reopen and move this into Firefox -> Developer Tools: Console.

Comment 4

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

I am going to guess that this depends on bug 987069, which would improve character encoding correctness across the JS engine.

Comment 5

[Nicolas Chevobbe [:nchevobbe]]

Pretty sure this is fixed because we also worked on this on Bug 1448553.
Going to close this, but anyone, feel free to reopen if it's still an issue