[w3ctag/design-reviews] FileSystemHandle::remove() for the File System Access API (Issue #773)

Wotcher TAG!

I'm requesting a TAG review of `FileSystemHandle::remove()` for the File System Access API.

Currently, it is not possible to remove a file or directory given its handle. You must obtain the handle of the parent directory, which [there is no straightforward way to do](https://github.com/whatwg/fs/issues/38) and may not be possible in some cases, and call `FileSystemDirectoryHandle::removeEntry()`.

Introducing a new method, `FileSystemHandle::remove()` (which follows the pattern of https://dom.spec.whatwg.org/#dom-childnode-remove), enables the common use case where you obtain a file handle from `showSaveFilePicker()`, but then decide you don't want to save after all, and delete the file.

  - Explainer: https://github.com/whatwg/fs/pull/9 
  - Tests: [FileSystemBaseHandle-remove.js](https://github.com/web-platform-tests/wpt/blob/master/file-system-access/script-tests/FileSystemBaseHandle-remove.js)
  - Security and Privacy self-review: [WICG/file-system-access/security-privacy-questionnaire.md](https://github.com/WICG/file-system-access/blob/main/security-privacy-questionnaire.md)
  - GitHub repo: [whatwg/fs](https://github.com/whatwg/fs/)
  - Primary contacts (and their relationship to the specification):
      - Austin Sullivan (@a-sully), Google Chrome
  - Organization(s)/project(s) driving the specification:Google/Chromium
  - External status/issue trackers for this specification: https://chromestatus.com/feature/6318478849998848 

Further details:

  - [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - The group where the work on this specification is currently being done: [whatwg/fs](https://github.com/whatwg/fs/) (initial work was started WICG, but the relevant parts to this proposal have been moved to whatwg)
  - The group where standardization of this work is intended to be done: [whatwg/fs](https://github.com/whatwg/fs/)
  - Major unresolved issues with or opposition to this specification: 
  - This work is being funded by: Google

We'd prefer the TAG provide feedback as:

  🐛 open issues in our GitHub repo for **each point of feedback**

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/773

You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/773@github.com>