Intent to Ship: Fetch API Body.formData for Request and Response

[Eero]

Contact emails

eero.h...@intel.com

Spec

https://fetch.spec.whatwg.org/#dom-body-formdata

Summary

This change allows multipart/form-data and application/x-www-form-urlencoded fetch requests and responses to be consumed and parsed into FormData objects.

Link to “Intent to Implement” blink-dev discussion

N/A

Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes.

Interoperability and Compatibility Risk

Firefox has implemented the property and has shipped it by 39.Given that the interface change is not big and we've already shipped similar arrayBuffer, blob, json and text methods, I think it's no problem to ship it for the Fetch API.

Is this feature fully tested by web-platform-tests?

Yes:

• https://w3c-test.org/fetch/api/request/request-consume-empty.html
• https://w3c-test.org/fetch/api/request/request-consume.html
• https://w3c-test.org/fetch/api/response/response-consume-empty.html
• https://w3c-test.org/fetch/api/response/response-consume.html
  

OWP launch tracking bug

https://crbug.com/718393

Entry on the feature dashboard

https://www.chromestatus.com/feature/5687725978025984

[Chris Harrelson]

LGTM1

--
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+unsubscribe@chromium.org.

[Rick Byers]

LGTM2

[Jochen Eisinger]

lgtm3