-
Notifications
You must be signed in to change notification settings - Fork 22.8k
Align status of Entries API docs with implementation reality #8379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
teoli2003
merged 1 commit into
main
from
sideshowbarker/file_and_directory_entries_api-status-update
Aug 27, 2021
Merged
Align status of Entries API docs with implementation reality #8379
teoli2003
merged 1 commit into
main
from
sideshowbarker/file_and_directory_entries_api-status-update
Aug 27, 2021
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3817142
to
c20dc1f
Compare
c20dc1f
to
62bb245
Compare
For all articles for features of the File and Directory Entries API, this change drops all flags and statements indicating the API is deprecated, non-standard, or experimental. The API has now been implemented and shipped for a long time now in all current browser engines — so at this point it’s not helpful to developers to warn them about it being unstable or non-standard. This change also makes a variety of other changes to align with the current specification — including: - replacing references to the obsolete FileError object with references to the DOMException object instead - dropping any mentions of the former parts of the specification that had to do with writing (creating) files (the current spec only defines an API for reading files) - dropping any mentions of the former parts of the specification that defines synchronous equivalents for some of the API members And the change also includes some fixes to un-conflate the File and Directory Entries API from the previous, ancient, non-standard File System API. Fixes #8263
62bb245
to
dc1cf8d
Compare
teoli2003
approved these changes
Aug 27, 2021
sideshowbarker
added a commit
to sideshowbarker/browser-compat-data
that referenced
this pull request
Sep 3, 2021
FileSystemDirectoryReader should never have been marked at deprecated. See mdn/content#8263 and see the spec at https://wicg.github.io/entries-api/#api-directoryreader Related MDN PR: mdn/content#8379
queengooborg
pushed a commit
to mdn/browser-compat-data
that referenced
this pull request
Sep 4, 2021
FileSystemDirectoryReader should never have been marked at deprecated. See mdn/content#8263 and see the spec at https://wicg.github.io/entries-api/#api-directoryreader Related MDN PR: mdn/content#8379
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For all articles for features of the File and Directory Entries API, this change drops all flags and statements indicating the API is deprecated, non-standard, or experimental. Fixes #8263.
The API has now been implemented and shipped for a long time now in all current browser engines — so at this point it’s not helpful to developers to warn them about it being unstable or non-standard.
This change also makes a variety of other changes to align with the current specification — including:
replacing references to the obsolete FileError object with references to the DOMException object instead
dropping any mentions of the former parts of the specification that had to do with writing (creating) files (the current spec only defines an API for reading files)
And the change also includes some fixes to un-conflate the File and Directory Entries API from the previous, ancient, non-standard File System API.