Open harrisi opened 1 year ago
This issue was fixed in Chromium yesterday, so it should land soon. For previous versions, it would still be nice to have this specified.
https://bugs.chromium.org/p/chromium/issues/detail?id=1418593
bug still present in chrome V118, so it will be at least next month before it (the fix) appears.
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 bothFileSystemSyncAccessHandle.read
andFileSystemSyncAccessHandle.write
, whereas the spec says anArrayBuffer
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
MDN page report details
* Query: `api.FileSystemSyncAccessHandle.write` * Report started: 2023-09-18T22:36:11.122Z