Editorial review: Add information on file system access locking modes

[chrisdavidmills]

Description

Chrome 121 supports a mode property on the options objects that can be specified as arguments to FileSystemFileHandle.createSyncAccessHandle() and FileSystemFileHandle.createWritable(). See the associated ChromeStatus entry. This PR adds content to explain these new features.

These features are not yet in the FileSystem API spec — see whatwg/fs#151 for the relevant PR. Consequently, I have marked them as non-standard in the associated docs.

See also the New Locking Scheme to Enable Multiple Readers and Writers explainer for more information on how it works.

Motivation

Additional details

Related issues and pull requests

Fixes mdn/mdn#479

[github-actions]

Preview URLs

• /en-US/docs/Web/API/FileSystemFileHandle/createSyncAccessHandle
• /en-US/docs/Web/API/FileSystemFileHandle/createWritable
• /en-US/docs/Web/API/File_System_API/Origin_private_file_system

Flaws (1)

Note! 2 documents with no flaws that don't need to be listed. 🎉

URL: /en-US/docs/Web/API/FileSystemFileHandle/createSyncAccessHandle
Title: FileSystemFileHandle: createSyncAccessHandle() method
Flaw count: 1

• macros:
  • Wrong xref macro used (consider changing which macro you use). Error processing path /en-US/docs/Web/API/DataView

External URLs (2)

URL: /en-US/docs/Web/API/FileSystemFileHandle/createSyncAccessHandle
Title: FileSystemFileHandle: createSyncAccessHandle() method

• https://createsyncaccesshandle-mode-test.glitch.me/ (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Web/API/FileSystemFileHandle/createWritable
Title: FileSystemFileHandle: createWritable() method

• https://createwritable-mode-test.glitch.me/ (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2024-08-09 09:24:44)

[tomayac]

Just some minor nits here and there.

[nathanmemmott]

Overall, the technical parts look correct to me.

[chrisdavidmills]

Thanks again for the technical review, @tomayac and @nathanmemmott. At this point, it looks like all your comments have been fixed, and I'm going to take the liberty of calling this tech review closed and move this on to the editorial review stage. Feel free to add further comments if needed.

[chrisdavidmills]

Awesome, cheers @sideshowbarker!