Closed
Bug 1330692
Opened 7 years ago
Closed 7 years ago
URLSearchParams constructor is not supported by our webidl codegen
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox54 | --- | fixed |
People
(Reporter: baku, Unassigned)
References
Details
Recently URLSearchParams CTOR is changed: [Constructor(optional (sequence<sequence<USVString>> or record<USVString, USVString> or USVString) init = ""), ... but record is not supported, and also without it, 'Constructor(optional (sequence<sequence<USVString>> or USVString) init = "")' gives syntax error.
Reporter | ||
Updated•7 years ago
|
Flags: needinfo?(bzbarsky)
Comment 1•7 years ago
|
||
record is kinda supported as MozMap. But it doesn't have quite the same semantics (e.g. is not order-preserving). We should probably modify MozMap to be named "record" and change its implementation to match the spec.
> and also without it, 'Constructor(optional (sequence<sequence<USVString>> or USVString) init = "")'
> gives syntax error
I don't get a syntax error here. I do get a codegen error because we don't support USVString as the type of the default value in handleDefaultStringValue. That should be pretty simple to fix.
Flags: needinfo?(bzbarsky)
Updated•7 years ago
|
Priority: -- → P3
Comment 2•7 years ago
|
||
When you add this, please add a test that the _key_ values are getting the USVString treatment.
Comment 3•7 years ago
|
||
Long since fixed when the dependencies got fixed.
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•