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 ?
Categories
(Core :: DOM: Core & HTML, enhancement, P3)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: baku, Unassigned)
References
(Blocks 2 open bugs)
Details
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.
|
||
Updated•7 years ago
|
Blocks: ServiceWorkers-compat
|
|
||
Comment 1•7 years ago
|
||
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.
|
||
Comment 2•7 years ago
|
||
The cache.put() case is specified already: use the entry and incumbent of the put() call.
|
|
||
Comment 3•7 years ago
|
||
Is there a spec issue tracking this? If so, please link it here. If not, file and link.
|
||
Updated•7 years ago
|
Priority: -- → P2
|
||
Comment 4•6 years ago
|
||
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
|
Assignee | |
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•