What's the right JSContext state to pass to cache::PutAll() in Cache::FetchHandler::ResolvedCallback ?

NEW
Unassigned

Status

()

enhancement
P3
normal
2 years ago
3 months ago

People

(Reporter: baku, Unassigned)

Tracking

(Blocks 2 bugs)

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

2 years ago
Cache::PutAll() can trigger JS execution in case the Request/Response body is a ReadableStream.
Currently we are using the JSContext in the state received by the FetchHandler promise resolving callback.

This could be wrong. The Streams API and the Fetch API don't covert this part yet.
Cache::PutAll() can also trigger directly from a cache.put() call in js.  We just pass the JSContext through there.  I assume it has the same question as comment 0.
The cache.put() case is specified already: use the entry and incumbent of the put() call.
Is there a spec issue tracking this?  If so, please link it here.  If not, file and link.
Priority: -- → P2
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.