- From: Jeffrey Yasskin <notifications@github.com>
- Date: Thu, 12 Feb 2015 15:56:37 -0800
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Thursday, 12 February 2015 23:57:07 UTC
Several algorithms contain steps like the following two: 1. Let p be [transforming responseArrayPromise with onFulfilled](http://www.w3.org/2001/tag/doc/promises-guide#transforming-by). 1. [Upon fulfillment of p with value](http://www.w3.org/2001/tag/doc/promises-guide#upon-fulfillment) responseArray, perform the following substeps, onFulfilled, in parallel: `onFulfilled` isn't defined except in the _Upon fulfillment_ substeps, but it's odd to see it used twice. In some cases, like [add()](https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#cache-add-method), the second use is inconsistent because it tries to resolve the already-fulfilled promise. Some other cases, like [addAll()](https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#cache-addAll-method), define `onFulfilled` twice, in different ways. I suspect you don't mean to use "Upon fulfillment" after "transforming" at all. --- Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/621
Received on Thursday, 12 February 2015 23:57:07 UTC