Implement the correct behavior for Cache.put when the Response has a termination reason

NEW
Unassigned

Status

()

3 years ago
3 years ago

People

(Reporter: Ehsan, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
Right now, nothing in our code even sets InternalResponse::mTerminationReason, so I assume the part of the spec where we're supposed to reject with a TypeError is not implemented.  We first need to fix our fetch implementation to set it properly and then make Cache respect it.
Blocks: 1110136
No longer blocks: 1110144
You need to log in before you can comment on or make changes to this bug.