Response.bytes not implemented yet in Chromium. Browser compatibility table contains incorrect data.

[JamesParrott]

What type of issue is this?

Incorrect support data. Response.bytes not implemented yet in Chromium.

What information was incorrect, unhelpful, or incomplete?

The summary table is incorrect. Response.bytes is not implemented in Google Chrome (any more than it is in Edge - the table is correct about that other column).

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet)

What did you expect to see?

Firefox:

let r = new Response();
undefined
r.bytes();
Promise { <state>: "pending" }

Brave:

let r = new Response();
undefined
r.bytes();
Promise {<fulfilled>: Uint8Array(0)}

Did you test this? If so, how?

Browser console.

Chrome (131.0.6778.265 Windows 11):

let r = new Response()
undefined
r.bytes()
Uncaught TypeError: r.bytes is not a function
    at <anonymous>:1:3

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

Incorrect information on MDN in this table: https://developer.mozilla.org/en-US/docs/Web/API/Response/bytes#browser_compatibility

Do you have anything more you want to share?

Feature implementation issue for Chromium: https://issues.chromium.org/issues/340206277

whatwg/fetch#1732

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/Response/bytes

MDN metadata

MDN page report details

• Query: api.Response.bytes
• Report started: 2025-01-16T21:30:40.822Z

[github-actions]

This issue was automatically closed because the title was left as the default, and a summary was not added.

If this is not a spam issue, please replace the <SUMMARIZE THE PROBLEM> part of the title with a short summary of the reported issue, and then post a follow-up comment. A maintainer will review your issue and reopen it if needed.

[JamesParrott]

Thanks Claas. I really appreciate it when nice humans review new issues.

As you've probably noticed however, before this was reopened, I jumped the gun and made what is now effectively a duplicate issue:
#25682

If someone knows how the {{compat}} field should be edited to make the information accurate, we can just close both!