New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Complete nodejs data for URL and URLSearchParams #13655
Conversation
"nodejs": [ | ||
{ | ||
"version_added": "10.0.0" | ||
}, | ||
{ | ||
"version_added": "7.0.0", | ||
"notes": "Has to be imported from the URL module." | ||
} | ||
], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This information for the URL
constructor is copied from the top-level object.
"nodejs": [ | ||
{ | ||
"version_added": "7.10.0" | ||
}, | ||
{ | ||
"version_added": "7.5.0", | ||
"partial_implementation": true, | ||
"notes": "Only string as <code>init</code> object supported." | ||
} | ||
], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the note because the information is covered by the later-added USVString
, record
, and sequence
sub-properties.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! 👍
Summary
Part of #13170. This fills in
true
and missingnodejs
values forURL
andURLSearchParams
.Test results and supporting details
Most of the data came from the "history" section of the documentation.
Local testing also revealed the oddity of
URL#searchParams
returning a dummy object in7.0.0
beforeURLSearchParams
was properly implemented in7.5.0
.