Ben Kelly [:bkelly, not reviewing] Reporter
	Description • 9 years ago

FetchEvent now extends ExtendableEvent which gives it a waitUntil() method:

https://github.com/slightlyoff/ServiceWorker/commit/ff93a4630866dcb9080bdf83fa5b82ddfed593a1

	Ben Kelly [:bkelly, not reviewing] Reporter
	Comment 1 • 9 years ago

Chrome actually implements this already and I see sites needing it all over the place.  I think we need it for v1 because devs are not going to try to feature detect this.

	Cătălin Badea (:catalinb)
	Comment 4 • 9 years ago

Please also remove mPromise and GetPromise from FetchEvent, these were used to extend the sw's lifetime when calling respondWith. I think respondWith should call waitUntil internally.

	(no longer active) Assignee
	Comment 5 • 9 years ago

(In reply to Cătălin Badea (:catalinb) from comment #4)
> Please also remove mPromise and GetPromise from FetchEvent, these were used
> to extend the sw's lifetime when calling respondWith. I think respondWith
> should call waitUntil internally.

Good point!  Filed bug 1218621.

	Boris Zbarsky [:bzbarsky]
	Comment 6 • 9 years ago

Comment on attachment 8678844 [details] [diff] [review]
Make FetchEvent inherit from ExtendableEvent

r=me

	Pulsebot
	Comment 7 • 9 years ago

https://hg.mozilla.org/integration/mozilla-inbound/rev/ac8844b56a54
https://hg.mozilla.org/integration/mozilla-inbound/rev/908842d5007b

	Carsten Book [:Tomcat]
	Comment 8 • 9 years ago

https://hg.mozilla.org/mozilla-central/rev/ac8844b56a54
https://hg.mozilla.org/mozilla-central/rev/908842d5007b

	Chris Mills [:cmills]
	Comment 9 • 9 years ago

The FetchEvent page already states that it inherits from ExtendableEvent, but I've added an explicit link to the waitUntil() page, just to be clear:

https://developer.mozilla.org/en-US/docs/Web/API/FetchEvent 

And a note was already added to the release notes:

https://developer.mozilla.org/en-US/Firefox/Releases/44#Service_Workers

So we're all good.