-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add the FileSystemObserver API #165
base: main
Are you sure you want to change the base?
Conversation
Gives each concept in the concepts section its own section.
Pulls out some implementation-defined concepts into a file system concept. This is so that the file system concept can be extended further in the future.
Pulls out some implementation-defined concepts into a file system concept. This is so that the file system concept can be extended further in the future.
320d58a
to
8047a41
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice if we could somehow specify more precisely what exact change events are triggered by changes to the bucket file system, since that should be entirely under control of user agents, so should be possible to be fully compatible between implementations. Not sure how to be go about doing that. Left a bunch of other comments as well...
e254c7d
to
86ed1e4
Compare
Defines the FileSystemObserver API, an API to observe file system change events. See whatwg#123 and WICG/file-system-access#72
86ed1e4
to
42a22b9
Compare
The errors causing the build to fail were not introduced by this PR. |
Add the FileSystemObserver API
Defines the FileSystemObserver API, an API to observe file system
change events.
See #123 and WICG/file-system-access#72
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff