api.FileSystem - File and Directory Entries API is (apparently?) now deprecated on Chrome

What type of issue is this?

Missing compatibility data

What information was incorrect, unhelpful, or incomplete?

Every interface for the File and Directory Entries API is listed as fully supported by Chrome. This is no longer true.

This includes:

• FileSystemDirectoryEntry
• FileSystemDirectoryReader
• FileSystemEntry
• FileSystemFileEntry
• FileSystem

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet)

What did you expect to see?

Some kind of obvious warning that this API is no longer in use on modern versions of Chrome. Chrome no longer even recognizes the interfaces and returns an error message stating they're undefined. I've been told this API has been replaced by the File System Access API.

Did you test this? If so, how?

I've tested it on both Microsoft Edge (111.0.1661.62) and a developer build of Chromium (110.0.5441.0).

I simply tried accessing the aforementioned interfaces through the inspector, to no avail. Of course, I also tried with an ordinary script, which is what initially lead to my confusion.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

Unfortunately, I don't have much else that might be useful. I'm just amazed nobody else has reported this earlier. I wish I knew how long this has been left untouched, or when Chrome decided to ditch this. I just know it's been at least a year, according to the person who had to help me figure out what was wrong over Discord.

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/File_and_Directory_Entries_API

MDN metadata

Start by locating the browser-compat-data entries for api.FileSystem and the related FileSystem* interfaces, then compare their Chromium-family data with the reported Edge 111 and Chromium 110 behavior. Check the linked MDN page and existing compatibility-data conventions; done means the affected records accurately reflect support status for the listed interfaces.