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 }}
Repository navigation
bug: URLSearchParams(null) behavior deviates from WHATWG standard / browsers #63559
Linux nixos 7.0.9 #1-NixOS SMP PREEMPT_DYNAMIC Sun May 17 15:16:34 UTC 2026 x86_64 GNU/Linux
Subsystem
URLSearchParams
What steps will reproduce the bug?
(newURLSearchParams(null)).toString()
How often does it reproduce? Is there a required condition?
Every time
What is the expected behavior? Why is that the expected behavior?
'null='
What do you see instead?
''
Additional information
When passing null to URLSearchParams constructor, Node.js deviates from the WHATWG URL and WebIDL specification, as well as the behavior in Chrome and Deno.
Activity
KhafraDev commentedon May 25, 2026
tbontb-iaq commentedon May 26, 2026
What version of Firefox are you using? On my Firefox (Firefox for NixOS 150.0.3 (64-bit)), it behaves the same as Chrome and Deno.
KhafraDev commentedon May 26, 2026
Oops, mistook the correct behavior for the bug...
marcopiraccini commentedon Jun 7, 2026
Here a small PR for this: #63782
url: fix URLSearchParams(null) to prudce null= per spec
url: fix URLSearchParams(null) to prudce null= per spec
url: fix URLSearchParams(null) to prudce null= per spec
url: fix URLSearchParams(null) to prudce null= per spec