Add locking mode options to FileSystemFileHandle #24038
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
data:api
queengooborg
approved these changes
Sep 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Chrome 121 supports a
modeproperty on the options objects that can be specified as arguments toFileSystemFileHandle.createSyncAccessHandle()andFileSystemFileHandle.createWritable(). See the associated ChromeStatus entry.These features are not yet in the FileSystem API spec — see whatwg/fs#151 for the relevant PR. Consequently, I have marked these additions as
"standard_track": false, and will mark 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.
Test results and supporting details
Related issues