-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
url: track status of a spec-compliant URLSearchParams #10821
Comments
What is the |
|
I've updated the status of issues in https://github.com/nodejs/node/projects/5. It's a good time to re-track the current status. |
In general I think most of the things listed as "waiting on spec" are no longer accurate and should be moved to "landed in spec". |
@domenic Thanks for the reminder, I have moved those items to "landed in spec" |
The entire `URLSearchParams` class is now fully spec-compliant. PR-URL: nodejs#12507 Fixes: nodejs#10821 Reviewed-By: James M Snell <[email protected]>
The entire `URLSearchParams` class is now fully spec-compliant. PR-URL: #12507 Fixes: #10821 Reviewed-By: James M Snell <[email protected]>
spec:
forEach()
argument type check (PR url: check forEach callback is a function #10905)sequence<sequence<USVString>>
andrecord<USVString, USVString>
(issue url: extend URLSearchParams constructor (whatwg #175) #10635, PR url: extend URLSearchParams constructor #11060)sort()
(issue url: add sort() to URLSearchParams #10760, PR url: add urlSearchParams.sort() #11098)USVString
(issue url: Improve WHATWG URLSearchParams spec compliance #9484 (comment), PR url: enforce valid UTF-8 in WHATWG parser #11436)spec irrelevant:
url
(issue url: export URLSearchParams alongside URL #10761, PR url: export URLSearchParams #10801)querystring changes:
/cc @nodejs/url
The text was updated successfully, but these errors were encountered: