You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
Chrome seems to be returning the decoded string for the URL. This may be creating the next problem where Chrome cannot create the web socket connection because the URL is undefined. Firefox loads the debugger page just fine.
api.js:1020 Uncaught (in promise) DOMException: Failed to construct 'WebSocket': The URL 'undefined' is invalid.(…)
WebInspector.WebSocketConnection @ api.js:1020
WebInspector.WebSocketConnection.Create @ api.js:1033
resolve @ index.js:32
connect @ index.js:30
connectTab @ chrome.js:52
(anonymous function) @ index.js:37callNext @ task.js:30
Promise.resolve.then.value @ task.js:36
I'm not seeing this error anymore, the websocket connection works, so I think we can close this even though the display is still incorrect.
Here's what I found about the issue.
Chrome is returning an IDN in Punycode though I'm not sure why because they display it correctly in their URL bar. IDN in Google Chrome explains the Chrome thinking around punycode but not for what we are seeing.
Because the WebSocket connection is being made and the debugger works I don't think we need to fix this right away.
I believe the official solution is the URL.domainToUnicode method. However it seems fairly unclear what the status of that API is going forward, it is not implemented in Firefox or Chrome. Servo has implemented the WHATWG method of URL.domainToUnicodeservo/servo#11629 and servo/servo#11632 yet the WHATWG actually removed the API here: whatwg/url#63 in favor of this different API: whatwg/url#64
Chrome seems to be returning the decoded string for the URL. This may be creating the next problem where Chrome cannot create the web socket connection because the URL is
undefined
. Firefox loads the debugger page just fine.Here's a test website: http://xn--80ahjdhy.xn--p1ai/
Screenshot of the difference at the tabs page:
The text was updated successfully, but these errors were encountered: