- From: Nathan Schloss <notifications@github.com>
- Date: Tue, 21 Feb 2017 11:39:49 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 21 February 2017 19:40:48 UTC
A service worker instance currently has no way to get it's current lifecycle state. There's a bit of a hack one can do where you keep track of the current event as a global variable but that's error prone and doesn't capture the waiting periods correctly. Imo, the best way to solve this would be to just allow a service worker to get it's ServiceWorker object somehow. Maybe via `self.worker` or `self.self` or something like that. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1077
Received on Tuesday, 21 February 2017 19:40:48 UTC