Timothy Gu

@stevenvachon The Node.js one is JS and not slow, because it was adapted from the optimized `querystring` implementation and made faster than `querystring` by getting rid of unneeded cruft. `whatwg-url`'s...

It's 2019. With https://jsbin.com/cafidayeri/1/edit?html,js,console,output, Firefox seems to allow any synthetic events to be fired on the element itself, except `click` events coming from the browser – precisely the spec behavior....

This technically isn't supported by Web IDL at the moment. Could you instead do ```js function toStringWithoutFragment(url) { const u2 = new URL(url); u2.hash = ''; return String(u2); } ```

See https://github.com/whatwg/url/pull/300/files#diff-03b21320f26423640f89c447968191e5R2381, https://github.com/whatwg/url/pull/300#issuecomment-297663843, https://github.com/whatwg/infra/issues/91

Just making sure, if there are multiple pairs with same name and value, all of such pairs will be deleted by the two-parameter variant, right?

Sorry, I missed that in my first reading. The idea SGTM. If people really want to do more advanced manipulations, there's always `new URLSearchParams(manip(Array.from(params)))`.

This issue now has 30 upvotes and 1 downvote, which would seem to be an "indication of common need". I think it's worth doing some work to investigate how feasible...

Right now, with the exception of drive letters, pathnames are pretty consistent between different schemes. I think it'd be unfortunate to have the slash-collapsing behavior just for `file` URLs. Additionally,...

This issue demonstrates a need for URLs such as `xn--x.com` to be preserved as `xn--x.com`, despite the Punycode decoding error. However, to prevent reparse bugs, we need to treat Unicode...

Check out the recent https://crrev.com/c/3088038 in Chromium, in particular this part: ``` Second, it changes the conditions required for removing host from Windows-only, any host, path has drive letter to...