Closed
Description
spec:
- Strictly maintain storage order (PR More URLSearchParams improvements #10399)
forEach()
argument type check (PR url: check forEach callback is a function #10905)Prototype properties enumerability (issue url: make URLSearchParams properties spec-compliant #10799, PR url: make URLSearchParams properties spec-compliant #11057)Constructor accepting asequence<sequence<USVString>>
andrecord<USVString, USVString>
(issue url: extend URLSearchParams constructor (whatwg #175) #10635, PR url: extend URLSearchParams constructor #11060)Implementsort()
(issue url: add sort() to URLSearchParams #10760, PR url: add urlSearchParams.sort() #11098)
spec irrelevant:
- Export on
url
(issue url: export URLSearchParams alongside URL #10761, PR url: export URLSearchParams #10801)Documentation (PR doc: add basic documentation for WHATWG URL API #10620)
querystring changes:
- Parsing ampersands (issue url: Improve WHATWG URLSearchParams spec compliance #9484 (comment), issue 'querystring.parse' works a inconsistent way with URLSearchParams(chrome) and python's urlparse.parse_qs #10454, PR querystring, url: repeated '&' in a paramsString will be skipped #10967, PR querystring: fix empty pairs handling #11234)Preserve parameter order in parsing
/cc @nodejs/url
Activity
joyeecheung commentedon Feb 17, 2017
What is the
Parameter order
issue in the OP referring to?TimothyGu commentedon Feb 17, 2017
new URLSearchParams('a=a&b=b&a=c').toString()
currently returnsa=a&a=c&b=b
watilde commentedon Apr 10, 2017
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.
domenic commentedon Apr 10, 2017
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".
joyeecheung commentedon Apr 11, 2017
@domenic Thanks for the reminder, I have moved those items to "landed in spec"
url: spec-compliant URLSearchParams parser