Adam Rice

@hayatoito is handling this in Chromium and has more context than me.

I don't feel like I could confidently write an explainer for this.

It seems you can get much the same functionality by abusing `URL.protocol.host`: ```js const c = new URL('https://example.com') c.host = '😀' '😀' c.host 'xn--e28h' c.host = 564 564 c.host '0.0.2.52'...

Agreed that RFC3986 seems to permit this. Given the low impact, this would be very low priority to implement.

https://wpt.live/url/url-setters.any.html has tests that expect to be able to set a username and password on a javascript URL. This makes me uncomfortable. Do you want me to file a separate...

Instead of "uncomfortable" how about "semantically meaningless"? IIUC, `javascript://` is a script containing a single comment. Setting `username` on it then modifies that comment to have an extra string at...

I made an example where giving the special non-special scheme treatment to a `javascript:` URL results in different behaviour: `javascript://host/1%0a//../0/;alert('non-opaque path');/%0aalert('opaque path');/..///` https://jsdom.github.io/whatwg-url/#url=amF2YXNjcmlwdDovL2hvc3QvMSUwYS8vLi4vMC87YWxlcnQoJ25vbi1vcGFxdWUgcGF0aCcpOy8lMGFhbGVydCgnb3BhcXVlIHBhdGgnKTsvLi4vLy8=&base=YWJvdXQ6Ymxhbms= This is obviously a very contrived example,...

@foolip I think we want to fix these. I think the linked bug for these issues is slightly different, so I newly filed https://crbug.com/1406728

Currently libzstd is not linked into Chromium. It would add roughly 700KB to the binary size (maybe can be trimmed a bit). This would be a hard sell if the...

We didn't do anything special in Chromium to reduce the size increase, except for only compiling in the decompression code. I think we were just lucky. I would like to...