Clarify that the File System Access API is not supported in Safari/Firefox #7129
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Caniuse's entry for the File System Access API currently specifies that Firefox/Safari partially support the File System Access API, with a note saying that they "only support the Origin Private File System (OPFS) part". This made sense when the API was originally introduced and everything, including the Origin Private File System, was in a specification with the name "File System Access".
However, since then, the specification has been split into two parts: the File System API (which is basically the OPFS and all browsers support) and the File System Access API (which only Chromium supports). So the definition of the term "File System Access API" has changed over the years and now specifically refers to only the part that allows for direct access to files/directories on the user's local file system. Therefore, saying that Firefox/Safari "partially support" the "File System Access API" does not make sense any more. Additionally, the note that "Desktop Chromium browsers currently support basic functionality and will be adding more of the API in the future" is also not true anymore; since Chromium v105, all features in the specification are supported afaik.
Somewhat related issue: #6615