Randell Jesup

The wpt tests assume that using a blob after the original file has been removed will reject with NotFoundError; this isn't in the spec (and may not be always possible...

I think we need snapshot state to be fully defined. The File API says it's set to the "state" of the file on disk; this could be interpreted to mean...

I would be in favor of renaming it - the current name is really bad. Of those, I like file.getPathRelativeTo(dir)

(I believe I know the answer to this): Do you need the ability to seek within these files? I presume performance reading (from WASM) is important here. Adding an 'accessMode:...

The discussion at the Breakout session on OPFS seemed to end with consensus on allowing an optional lock-type parameter, which defaults to exclusive, but allows taking a shared read lock,...

The spec currently requires a shared lock for WritableFileStream (which blocks a SyncAccessHandle while we have a WritableFileStream) I'm not going to address interactions with the non-OPFS File System API....

WritableFileStream right now takes a shared lock (which also allows for all sorts of oddities depending on who closes it last). It could also take a lock-type option for an...

We've updated (locally at least) the WPTs to not allow remove/etc if there's a WFS - we require an exclusive lock to remove or move a file. Do current applications...

The argument for multiple writers would be that it allows a simpler (and perhaps more efficient) emulation of POSIX file operations by e.g. emscripten/etc - POSIX doesn't disallow multiple opens....

You can't get the size without reading it in? What about getSize()? What's the usecase for these with regards to OPFS? (I can see perhaps being more relevant for the...