Add readable response and FetchEvent vertical - #298
Merged
Merged
Conversation
Collaborator
Author
|
Windows C2026 follow-up is now on the PR head in
A local native rebuild could not regenerate because its previously cached V8 source/output tree was removed; the pushed CI run is the clean compilation gate. The unrelated pre-existing IndexedDB C2026 remains outside this PR's ownership. |
This was referenced Sep 17, 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.
Problem
The service-worker control plane can activate and claim a Code OSS webview, but WebScene has no readable response body or
FetchEvent.respondWith()vertical. A controlled resource therefore cannot return even a static streamed response, and snapshot-created iframe realms omit the fetch globals entirely.Change
ReadableStream, default reader/controller, cancellation, close/error ordering, locking, andtee()Responseown a live body stream with clone/tee andbodyUsedconsumption semanticsExtendableEventandFetchEventwith client/request attributes,waitUntil(),respondWith(), andhandled206response dispatch and install the same body globals in top-level and nested snapshot realmsThis is Stack A for #266. The issue stays open. Unchanged Markdown still depends on the next stacked CacheStorage empty-match/request-routing and TransformStream tranche; this PR does not claim full Code broker or product rendering acceptance.
Validation
service-worker-fetch: pass; 100 cycles, p95 0.208042 ms, V8 heap 1,144,292 → 1,144,292 bytesservice-worker-lifecycle: pass; 100 cycles, p95 6.03821 ms, registration high-water 1service-worker-clients: pass; 100 cycles, p95 0.091792 ms, queue cap 256, peak RSS 49,938,432 → 63,160,320 bytesgit diff --check: pass