Skip to content

bug: URLSearchParams(null) behavior deviates from WHATWG standard / browsers #63559

Description

@tbontb-iaq

Version

v24.16.0

Platform

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?

(new URLSearchParams(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

Image

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

  1. KhafraDev commented on May 25, 2026

    @KhafraDev
  2. tbontb-iaq commented on May 26, 2026

    @tbontb-iaq
    Author

    Firefox behaves the same as node.

    Image

    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.

  3. KhafraDev commented on May 26, 2026

    @KhafraDev
    Member

    Oops, mistook the correct behavior for the bug...

  4. added
    whatwg-urlIssues and PRs related to the WHATWG URL implementation.
    on Jun 1, 2026
  5. marcopiraccini commented on Jun 7, 2026

    @marcopiraccini
    Contributor

    Here a small PR for this: #63782

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    whatwg-urlIssues and PRs related to the WHATWG URL implementation.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions