fetch event respondWith() should report progress back to original document

RESOLVED WORKSFORME

Status

()

Core
DOM
RESOLVED WORKSFORME
3 years ago
3 years ago

People

(Reporter: bkelly, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
Talking in #whatwg channel today, the topic of network progress events to the document came up.  In particular, if a SW does this, then we should be reporting network progress for the fetch();

  event.respondWith(fetch(url))

Note, we don't know the fetch() Response is associated with the document until event.respondWith() is called.

At that point, though, we should ideally set the nsIProgressEventSink from the document on the Response's underlying nsIChannel.  We might have to also somehow proxy through the original request so that the document associates the progress correctly.

If the Response has fully consumed the nsIChannel at this point, and the channel is closed, then we cannot report progress.  We could send a 100% progress callback or simply do nothing in this case.

We should also make sure this is set up correctly for Response's returned from event.default().

Not sure we need this before pref'ing on, but setting the dependency there as I don't see a follow-on meta bug.
we think this is done.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.