Repository navigation
Observe opaque file handles for watcher refresh - #441
Merged
Merged
Conversation
This was referenced Sep 18, 2026
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
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.
Unchanged VS Code silently skips HTMLFileSystemProvider.watch() when FileSystemObserver is absent. This adds a browser-shaped observer over existing opaque file and directory grants, with bounded non-overlapping 250 ms snapshots, recursive traversal caps, appeared/disappeared/modified/errored records, and unobserve/disconnect cleanup.
The implementation unblocks the local watcher boundary in #252 and the external-edit/save reconciliation path in #269. It does not expose native paths or add a VS Code shim.
Closes #438
Validation debt: current implementation-only priority explicitly skips tests, benchmarks, packaged acceptance, and CI waiting. #438 records the Chrome/WPT, native lifecycle, VS Code product, and performance gates that remain to be run.