Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
FSA: Fail to create a writable if the file does not exist
DO NOT MERGE (yet) whatwg/fs#125 Currently, the createWritable() algorithm specifies that we must throw a NotFoundError if the file corresponding to the FileSystemHandle does not exist. See https://fs.spec.whatwg.org/#dom-filesystemfilehandle-createwritable Unfortunately, this does not match the behavior that has been implemented in Chrome for a very long time; specifically that - createWritable({ keepExistingData: true }) fails if the file does not exist, since there is no existing data to copy to the swap file - createWritable({ keepExistingData: false }) succeeds if the file does not exist, since there is no existing data to copy. It still fails if the parent directory does not exist, however Bug: 1405851 Change-Id: I788c5b177c188862d4b08b5dd876404522fa32d5
- Loading branch information