Contact emails asu...@chromium.org, ds...@chromium.org
Specification https://github.com/whatwg/fs/pull/76 https://github.com/whatwg/fs/pull/82 Summary We’re adding a cursor to FileSystemSyncAccessHandle <https://developer.mozilla.org/en-US/docs/Web/API/FileSystemSyncAccessHandle>, matching the behavior of the FileSystemWritableFileStream <https://developer.mozilla.org/en-US/docs/Web/API/FileSystemWritableFileStream/write> API (the other way to write files using the File System Access API). Until now, failing to specify the optional at: parameter while reading or writing would set the offset of the operation to 0. In practice, this effectively required the parameter to be specified for every operation (and it was actually required until recently <https://groups.google.com/a/chromium.org/g/blink-dev/c/BboiMXq2-xg/>). Given this, we expect a low likelihood of site breakage. Starting in M111 <https://chromiumdash.appspot.com/commit/02799cd0b2c94598ae63ba14bf096c608ff3f1f8>, read and write operations will instead default to the position of an internal cursor that is updated with every read, write, and truncate operation. Before: position += handle.write(data1, {at: position}); position += handle.write(data2, {at: position}); After: handle.write(data1); handle.write(data2); Blink component Blink>Storage>FileSystem <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EStorage%3EFileSystem> Tracking bug crbug.com/1394790 Estimated milestone M111 -- 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/CAGnvaEW0uy7u6eati%2BkKmVJPW718waY50jG48_K4J_EFJh6gYg%40mail.gmail.com.
