> Just a heads-up, the File System Access API is underway in Chrome, which potentially removes nearly all of the absurdity here. It doesn't. Because there are

> Just a heads-up, the File System Access API is underway in Chrome, which potentially removes nearly all of the absurdity here. It doesn't. Because there are now 4 different file access api proposals. At least one of them is already in Chrome (File System Access). [1] Both Safari and Mozilla are unwilling to implement any of the four until the mess is cleaned up, and there's a single coherent proposal. Chrome, of course, doesn't care. Storage Foundation API in addition to File System Access they already implemented. [1] https://github.com/WICG/storage-foundation-api-explainer/issues/4 https://github.com/WICG/storage-foundation-api-explainer/iss...