Open Bug 1384006 Opened 7 years ago Updated 2 years ago

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


(Core :: DOM: Core & HTML, enhancement, P3)





(Reporter: baku, Unassigned)


(Blocks 2 open bugs)


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 for more information
Priority: P2 → P3
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.