we (web engine): Experimental web browser project to understand the limits of Claude
2
fork

Configure Feed

Select the types of activity you want to include in your feed.

Enforce fetch body locking and cancellation semantics #202

open opened by pierrelf.com

Phase 20 requires Response.body as a ReadableStream with body locking semantics and cancellation propagated to the underlying HTTP connection. Audit and harden fetch/Response behavior for bodyUsed, getReader() locking, cancellation, cloning, and stream errors.

Acceptance criteria:

  • Response.body is locked while a reader is active and bodyUsed flips on consumption.
  • text(), arrayBuffer(), and stream readers reject when the body was already consumed.
  • Response.clone() follows stream tee semantics for unread bodies and fails for used bodies.
  • reader.cancel() propagates to the underlying response body reader/connection where available.
  • Add focused tests covering bodyUsed, clone, cancel, and mixed helper/reader consumption paths.
sign up or login to add to the discussion
Labels

None yet.

assignee

None yet.

Participants 1
AT URI
at://did:plc:meotu43t6usg4qdwzenk4s2t/sh.tangled.repo.issue/3mm23seagis2w