UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3218.0 Safari/537.36

Steps to reproduce the problem:
gᴏᴏgle.com is show as xn--ggle-q33aa.com in addressbar, because the o are small capital letters.
xn--xnggle-q33aa-ht4s.com is shown as xn一ggle-q33aa.com.

I used U+4e00 instead of two dash.

xn一ggle-q33aa.com
xn--ggle-q33aa.com

What is the expected behavior?
I am not sure about the real risks, but U+4e00 and latin characters could be a problem in the way they are shown at the moment.
But faking xn notation of xn fakes might not be a real problem. Probably it is a fishing problem simulating a xn- notation and not being one. It might weaken the concept of showing xn notation to make the people feel safer.

What went wrong?
Japanese script allows latin characters to be combined with japanese characters.
https://www.verisign.com/assets/languagefiles/JPN.html

I used a long bar to simulate the two - from xn--.

Did this work before? No 

Chrome version: 63.0.3218.0  Channel: dev
OS Version: 
Flash Version: 

I am not sure what Identifier_Status U+4e00 has.