Contact emails
asu...@chromium.org,
m...@chromium.orgSpecification
https://github.com/WICG/file-system-access/pull/317Summary
Currently, the File System Access API does not support an efficient way to move or rename files or directories. This requires creating a new file/directory, copying over data (recursively, in the case of a directory), and removing the original. This process is slow, error prone (e.g. disk full), and can require re-uploading files in some cases.
Blink component
Blink>Storage>FileSystemTAG review
Not yet requestedTAG review status
Not applicableRisks
Interoperability and Compatibility
Gecko: No signal
WebKit: No signal
Web developers: Strongly positive (
https://github.com/WICG/file-system-access/issues/65)
Security
Writes to the Origin Private File System skip Chrome's Safe Browsing checks. Moving these files out of the OPFS to a directory on the user's system is a use case we want to support, so we will perform safe-browsing checks on these moves.
Goals for experimentation
Ongoing technical constraints
Debuggability
N/A
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
NoThe File System Access API is not exposed on Android
YesFlag name
FileSystemAccessAPIExperimental
Requires code in //chrome?
FalseEstimated milestones
No milestones specified
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5640802622504960