api.FileSystemSyncAccessHandle.read/write - Chromium-based browsers do not allow passing an `ArrayBuffer`

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?

Chromium-based browsers only accept ArrayBufferView as the first parameter to both FileSystemSyncAccessHandle.read and FileSystemSyncAccessHandle.write, whereas the spec says an ArrayBuffer should be accepted (https://webidl.spec.whatwg.org/#AllowSharedBufferSource).

What browsers does this problem apply to, if applicable?

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

What did you expect to see?

A note on Chromium browsers that they don't implement the spec fully.

Did you test this? If so, how?

Yes, I have a site that was trying to write an ArrayBuffer that failed in Chromium-based browsers.

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

No response

Do you have anything more you want to share?

While the issue is linked only to FileSystemSyncAccessHandle.write, .read is also not fully implemented, as can be seen in the source. I have not yet opened in issue for Chromium.

MDN URL

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

MDN metadata

Start with the browser-compat-data entries for api.FileSystemSyncAccessHandle.write and the corresponding read API, using the MDN URL and Chromium source link in the report. Check how browser-specific limitations are represented, then ensure the data records Chromium's ArrayBuffer restriction for both methods and validates successfully.