- From: Jake Archibald <notifications@github.com>
- Date: Mon, 16 Feb 2015 08:44:25 -0800
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Monday, 16 February 2015 16:44:54 UTC
My take: I don't think asleep tabs should have an effect on the lifecycle within a registration. These tabs are going to reload anyway, having them reload with an updated version seems fine. Given that tab-management is pretty much a lost art in Android L, you'd very easily end up with old forgotten tabs preventing updates becoming active. Having asleep tabs show up in `clients.getAll()` is somewhat desirable, as following a push message you can focus one of these existing tabs rather than opening a new one. However, given that tab management isn't really a thing anymore in Android L, maybe it doesn't matter if you open a new window vs focusing an asleep one. I don't think there's a performance benefit. (I realise this is a bit Android-specific, so interested in hearing from other vendors) --- Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/626#issuecomment-74537053
Received on Monday, 16 February 2015 16:44:54 UTC