api.Navigator.sendBeacon - Chromium "Blob issue" was fixed in browsers based on Chromium 81+

What type of issue is this?

Incorrect support data (example: Chrome says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

There's are compatibility-remark on Chrome browser saying that Blob ain't supported from Chrome 39 and forward.
But this was fixed in Chrome 81:
https://bugs.chromium.org/p/chromium/issues/detail?id=724929
I assume it is also fixed in other Chromium based browsers.

I can also confirm it is working in Chrome 112.

What browsers does this problem apply to, if applicable?

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

What did you expect to see?

I was expecting a remark for Chrome 39-80 only (and equivalent for other Chromium based browsers)

Did you test this? If so, how?

I can also confirm it is working in Chrome 112 in an in-house (intranet) application.

From Chrome the following sends an object (sat) as JSON to url.href:

        const headers = {
            type: 'application/json'
        };
        const blob = new Blob([JSON.stringify(sat)], headers);
        const ok = navigator.sendBeacon(url.href, blob);

It is received in backend as expected.

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

https://bugs.chromium.org/p/chromium/issues/detail?id=724929

Do you have anything more you want to share?

No response

MDN URL

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

MDN metadata

MDN page report details

• Query: api.Navigator.sendBeacon
• Report started: 2023-05-02T06:04:25.813Z

Start with the api.Navigator.sendBeacon compatibility-data entry and the linked Chromium issue; inspect the existing Blob remarks for Chrome, Edge, Opera, and Samsung Internet. Done means the remark is limited to the affected pre-Chromium-81 versions and the reported Chromium-based browser entries reflect the fix.