[ServiceWorker] Resolve Job Promise can resolve jobs with an incorrect value (#829)

Currently the Resolve Job Promise algorithm resolves all equivalent jobs with the same value, I don't think this is correct. For example multiple equivalent register jobs should possibly be resolved with distinct `ServiceWorkerRegistration` instances (if they were called from different javascript contexts). But maybe more importantly, two equivalent jobs can have different `client` properties; this means that for example with a register job each equivalent promise needs a `ServiceWorkerRegistration` instance with a different associated service worker client.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/829

Received on Friday, 5 February 2016 19:37:31 UTC