Thomas Steiner

You may want to investigate the [Origin Private File System](https://web.dev/file-system-access/#accessing-files-optimized-for-performance-from-the-origin-private-file-system). FYI, the SQLite team are looking into this as well for their [upcoming Wasm port](https://developer.chrome.com/blog/deprecating-web-sql/#where-to-go-from-here).

> Thanks for the review @tomayac , this was really helpful, and lead to some improvements in the text and code examples. You're welcome, thanks to _you_ for documenting this!...

Thank _you_ again. FWIW, added `Critical-CH` to the content backlog, so it doesn't fall through the cracks.

FYI: There's now an [`EyeDropper`](https://developer.mozilla.org/en-US/docs/Web/API/EyeDropper) API in Chromium-based browsers. This component could probably use it.

> Tada: https://github.com/jimmywarting/native-file-system-adapter We offer a similar library: [browser-nativefs](https://github.com/GoogleChromeLabs/browser-nativefs). Its API deliberately differs from the native API.

Do you have plans on adding Native File System API support to StreamSaver.js? If so, happy to help.

> Saw you lib after i uploaded my adapter to the public > yours is more like a shim than a polyfill or ponyfill (but without the sandboxing features) True,...

Especially like the idea that this would take care of sub resources. 👍

Still waiting for the spec.

It is, but we're still waiting for https://github.com/w3c/manifest/issues/676 to get closed.