Request for Position: FileSystemHandle Remove Self

[a-sully]

Request for position on an emerging web specification

• WebKittens who can provide input: @annevk, @szewai

Information about the spec

• Spec Title: FileSystemHandle Remove Self
• Spec URL: Add FileSystemHandle.remove method whatwg/fs#9
• GitHub repository: https://github.com/whatwg/fs
• Explainer: Explainer for FileSystemHandle.remove() a-sully/fs#1

Design reviews and vendor positions

• TAG Design Review: FileSystemHandle.remove() for the File System Access API w3ctag/design-reviews#773
• Mozilla standards-positions issue: FileSystemHandle Remove Self mozilla/standards-positions#716

Anything else we need to know

The explainer focuses mainly on the use cases outside of the Origin Private File System, but within the OPFS this method is (just) a significant improvement in API ergonomics.

[annevk]

What happens for (await navigator.storage.getDirectory()).remove({ recursive:true })?

It seems like in theory that ought to work as you have write access, but map["root"] will continue to exist, making subsequent invocations result in spec-UB I think. That looks like it needs some work.

This looks reasonable to me though.

[a-sully]

Good point - the WPTs assert that you can't remove a root, but it's not currently in the spec language. I can fix that

[a-sully]

Oh just kidding, this is already covered. Conversation is happening here https://github.com/whatwg/fs/pull/9/files#r1042179453

[annevk]

Based on the linked PR I suggest we label this as "position: support" seven days from now.

[hober]

Closing as we've identified our position.