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
file:// URLs on Windows typically do not %-encode the colon after the drive letter. When building such URIs, this library drops the host of the base (I assume because it reads it as a port?)
Looks to me like that is because in the URL spec in the path state instruction 1.4.1.1 does not use the base URL host.
Open a bug in the official repo if you think that's a bug in the spec.
Closing because I don't think that's a bug in whatwg-url, but can reopen if you think I followed the spec wrong.
file://
URLs on Windows typically do not %-encode the colon after the drive letter. When building such URIs, this library drops the host of the base (I assume because it reads it as a port?)Expected, Chrome:
Actual, whatwg-url:
It actually happens even when you just set
pathname
to anything with a colon:The text was updated successfully, but these errors were encountered: