The URLSearchParams interface allows developers to (shock!) manipulate the search params of a URL. It also provides a mechanism to POST data via `fetch()` with a urlencoded body vs. the multipart body that `FormData` produces.
Shipping this feature increases our adherence to the URL spec, and lowers the gap between Chrome and Firefox in terms of the available interfaces, which will make developers happy.
I'm poking at this right now because `URLSearchParams` will enable developers to submit urlencoded data as the body of a POST via `fetch()`. That's a requirement we've heard from developers who are experimenting with the Credential Management API (https://w3c.github.io/webappsec-credential-management/), and this seems like the cleanest way of offering the functionality.
Low. Firefox shipped this interface in 29 (https://bugzilla.mozilla.org/show_bug.cgi?id=887836), and it's a fairly stable part of the URL spec. I've put up a PR to add tests to web platform tests; they pass (with 2 tiny exceptions) in both Firefox and Chrome: https://github.com/w3c/web-platform-tests/pull/2326.
Ongoing technical constraints
I've extracted the core of `URLSearchParams` out of Sigbjorn's excellent patch at https://codereview.chromium.org/143313002/. The integration with `URL` can't happen until Node moves to Oilpan. I'm assured that this will happen Real Soon Now(tm).
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
OWP launch tracking bug
Link to entry on the feature dashboard
Requesting approval to ship?
Yes. I'd like to ship the pieces of this interface that we can ship today, and ship the integration with other interfaces once Oilpan ships.
That is, the `URLSearchParams` interface will exist, and objects can be created and manipulated, and passed to Fetch. The `URL::searchParams` property will not exist until Oilpan ships.
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
Den 11/16/2015 11:32, Philip Jägenstedt skreiv:
It seems fine that URL.searchParams isn't implemented yet, since it's
apparently only a convenience.
It's time to support the .searchParams attribute on URL; now made notionally easier by Oilpan finally being done.
https://codereview.chromium.org/1860623002/ adds it. Should I consider the LGTMs here to apply to finally ship this attribute also? (For reference, the original intent: https://groups.google.com/a/chromium.org/d/msg/blink-dev/grHZDbldP04/JdsoQ169AQAJ )