Hi Austin, I've been skimming through the history here but am left a little confused about how exactly this fits into the larger file system picture. When you shipped <https://groups.google.com/a/chromium.org/g/blink-dev/c/tESXuOfqQMQ/m/w-tvoCPYCQAJ> 'remove' I gather that was for both OPFS and local file use cases, is that right? Why is this intent scoped to just local file use cases? I know the other engines don't support local file system access, but their opinion (and TAG's opinion) on the API for OPFS cases seems relevant to how we reason about this intent. But as long as we're asking for signals specific to the local file system use case, I wouldn't expect that we'll get anything of value (as in the Mozilla standards position response <https://github.com/mozilla/standards-positions/issues/732#issuecomment-1396391008>). I see there's a chromestatus entry <https://chromestatus.com/feature/5640802622504960> for move generally, what's the status of that? Any reason why we can't focus on getting consensus for move() generally as supported broadly in OPFS, and then separately talk about details (if any) for local access?
Thanks, Rick On Fri, Jan 20, 2023 at 4:51 PM Austin Sullivan <asu...@chromium.org> wrote: > Contact emails > > asu...@chromium.org > > Specification > > https://github.com/whatwg/fs/pull/10 > > Design docs > > https://github.com/a-sully/fs/pull/2 > > Summary > > Support efficient moves and renames of local files (i.e. user-visible > files on the device) with the File System Access API. > > Efficient file moves is a core API primitive that dramatically improves > the viability of a number of applications on the web. For example, renaming > a large video file currently requires obtaining access to a new file, > copying all the data, and removing the original. This is slow, error-prone > (ex: out of quota), and a poor developer and user experience. > > > Blink component > > Blink>Storage>FileSystem > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EStorage%3EFileSystem> > > Search tags > > file <https://chromestatus.com/features#tags:file>, system > <https://chromestatus.com/features#tags:system>, access > <https://chromestatus.com/features#tags:access>, move > <https://chromestatus.com/features#tags:move>, rename > <https://chromestatus.com/features#tags:rename>, opfs > <https://chromestatus.com/features#tags:opfs> > > TAG review > > https://github.com/w3ctag/design-reviews/issues/805 > > TAG review status > > Pending > > Risks > Interoperability and Compatibility > > Gecko: Negative to local file access more broadly, and therefore this > addition (https://github.com/mozilla/standards-positions/issues/732) > > WebKit: No signal on this addition ( > https://github.com/WebKit/standards-positions/issues/121) or local file > access in general (https://github.com/WebKit/standards-positions/issues/28 > ) > > Web developers: Strongly positive ( > https://github.com/WICG/file-system-access/issues/64) > > Other signals: > > Ergonomics > > See the "Improve the ergonomics of the API" section of the explainer > > Security > > See the "Security Considerations" section of the explainer > > WebView application risks > > N/A > > Debuggability > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)? > > No, accessing local files with the File System Access API is not > supported on Android > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ? > > Yes > > Flag name > > kFileSystemAccessMoveNonOpfsFiles > > Requires code in //chrome? > > False > > Launch bug > > https://launch.corp.google.com/launch/4200956 > > Estimated milestones > > M111 > > Anticipated spec changes > > No anticipated inter-op issues with file moves. Directory moves are being > punted for now while we resolve inter-op issues (see > https://github.com/whatwg/fs/issues/59 for more context) > > Link to entry on the Chrome Platform Status > > https://chromestatus.com/feature/6271579653144576 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > -- > 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/CAGnvaEXisJRYpRYJtRW%2BYiN_eL27opNRvjH6U3v0R6nHV8tEtA%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGnvaEXisJRYpRYJtRW%2BYiN_eL27opNRvjH6U3v0R6nHV8tEtA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAFUtAY8vAkurYhvSSpyO8V%2BZRD2-sYJ0rzCQei%3DjBdAoWFSPqA%40mail.gmail.com.
