Re: [whatwg/url] searchParams.set("param", undefined) should not stringify as param=undefined (#427)

I think if Chrome was willing to make this change (and also for `get()`, it should not diverge) and they don't get reports that's probably evidence enough. It seems rather unlikely it becoming "`undefined`" is something a server relies on, but as you say, it's hard to prove.

cc @domenic (sorry, not sure who from Chrome deals with this API)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/427#issuecomment-458455643