Austin Sullivan

Ah, thank you for bringing this up! https://github.com/whatwg/fs/issues/19 had two parts - some proposals around file locking and in-place writes, and the `autoClose` flag. I closed it since the locking...

FYI some discussion about this is happening over on https://crbug.com/1464953

FYI merge conflicts are due to https://github.com/WICG/file-system-access/commit/dd9f1f9fddc6cf66c0250314012251cfd31b6650

> I just ran in to a similar thing around logging. Suppose the user wants to select a text file to add log entries to. The natural thing to do...

`move()` for local files should be available [on recent versions of Chromium](https://chromestatus.com/feature/6271579653144576). See the explainer: https://github.com/whatwg/fs/blob/main/proposals/MovingNonOpfsFiles.md Directory moves were not feasible for a long time due to infrastructural inconsistencies that...

note: directory moves are still not supported on Chromium browsers. Re-opening this issue to track this feature request

This gives warnings when building locally because `[=file system entry/request access=]` and `[=file system entry/query access=]` aren't marked for export in whatwg spec. You'd put up a PR way back...

Filed a bug to fix the document the inconsistencies on the implementation side https://crbug.com/1231268

This is related to #369 in that they're both asking for bundled permissions, but unfortunately the solution there (see https://github.com/WICG/file-system-access/issues/369#issuecomment-1376641188) won't help with the use case of upgrading multiple read-only...

Well done, bot. This is due to https://github.com/whatwg/fs/pull/96. I'll put up a fix soon