Contact emails
perryuw...@chromium.org

Explainer
None


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


Summary

Add a bytes() method to the Request and Response interfaces, which returns a 
promise that resolves with a Uint8Array. While Request and Response have an 
arrayBuffer() method, we can't read directly from a buffer. We have to create a 
view such as a Uint8Array to read it. The bytes() method improves the 
ergonomics of getting the body of Request and Response.



Blink component
Blink>Network>FetchAPI


TAG review
None


TAG review status
Issues addressed


Risks




Interoperability and Compatibility

None


Gecko: Shipped/Shipping (https://bugzilla.mozilla.org/show_bug.cgi?id=1896475)

WebKit: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=274102)

Web developers: No signals

Other signals:


Activation

The feature can be easily polyfilled.



Security

The feature adds no capabilities that developers don't already have. The 
implementation mostly reuses existing logic, reducing the security risk.



WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it 
has potentially high risk for Android WebView-based applications?

None




Debuggability

Automatically supported as a feature implemented in WebIDL.



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, 
ChromeOS, Android, and Android WebView)?
Yes


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


Flag name on chrome://flags
FetchBodyBytes


Finch feature name
None


Non-finch justification
None


Requires code in //chrome?
False


Tracking bug
https://issues.chromium.org/issues/340206277


Estimated milestones


Shipping on desktop 132

Shipping on Android 132

Shipping on WebView 132




Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop 
issues. Please list open issues (eg links to known github issues in the project 
for the feature specification) whose resolution may introduce web 
compat/interop risk (eg, changing to naming or structure of the API in a 
non-backward-compatible way).
None


Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5239268180754432?gate=6644384851034112


This intent message was generated by Chrome Platform Status.

-- 
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+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/66ffc642.2b0a0220.d54b7.14c4.GAE%40google.com.

Reply via email to