doc: fix history info for URLSearchParams

[skyclouds2001]

Refs: #17365
Refs: #9484
Refs: #7448
Refs: #10801
Refs: mdn/browser-compat-data#24998

Add version table for:

• new URLSearchParams(string)
  • added in v7.5.0, taken from bcd
  • backlogged to v6.13.0, see Backport WHATWG URL to 6.x #17365
• URLSearchParams.prototype.{entries,forEach,keys,values}
  • added in v7.3.0, see url: Improve WHATWG URLSearchParams spec compliance #9484
  • backlogged to v6.13.0, see Backport WHATWG URL to 6.x #17365
• other methods & properties
  • mostly added (if doesn't have version table previously) in v7.0.0, see url: adding WHATWG URL support #7448, and then backlogged to v6.13.0

Test screenshots taken from mdn/browser-compat-data#24998:

[lpinca]

The class was added in v7.5.0 and the constructor in v7.0.0 🤔 ?

[skyclouds2001]

oops! my mistake

[aduh95]

I don't think those additions are adding much, it's already implied that if there are no history data, it inherits from the class, having redundant info only increases the risk to let a mistake pass through

[aduh95]

OK, so the nuance is that require('url').URLSearchParams only existed after 7.5.0 (021338d), but the actual class was added along the rest of the URL API (a8ece14) and was accessible via new URL().searchParams. I wonder if any of our user would be sensible to the nuance – hopefully there are no v7.x users left so it doesn't matter anyway.

[skyclouds2001]

It's true that this history info may be useless for users (it's quite impossible to see v7.x users left)

But it is required in some cases, like browser-compat-data. And it is normal way to add history info for every single feature (especially for new features, like web crypto, web stream, worker threads). Also, parent feature and children feature are not always have the same history info, like in this PR.

[aduh95]

The commit message does not match the changes

[skyclouds2001]

The commit message does not match the changes

Fixed!

[github-actions]

This pull request has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.