Service Worker "Update on reload" state impacted by other devtools instances
Reported by
ja...@apphaus.co.uk,
Mar 16 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36 Steps to reproduce the problem: Closing a second devtools instance; 1. Open a page with a Service Worker 2. Open devtools and enable "Update on reload" in the Application panel under Service Workers 3. Open a second tab to any page and open dev tools for this tab 4. Close dev tools in the second tab 5. Return to the first tab, reload the page and note that "Update on reload" remains checked however it is ineffective Changing the "Update on reload" state in a second devtools instance; 1. Open a page with a Service Worker 2. Open devtools and enable "Update on reload" in the Application panel under Service Workers 3. Open a second tab to any page and open dev tools for this tab 4. In the second tab, disable "Update on reload" in the Application panel under Service Workers 5. Return to the first tab, reload the page and note that "Update on reload" remains checked however it is ineffective What is the expected behavior? 1. "Update on reload" continues to remain in effect 2. "Update on reload" state is not impacted by other devtools instances What went wrong? Opening and closing a second devtools instances appears to have rendered "Update on reload" ineffective in the original devtools instance. Enabling/disabling "Update on reload" in a second devtools instance also impacts the "Update on reload" option in the first devtools instance. Did this work before? N/A Chrome version: 57.0.2987.98 Channel: stable OS Version: OS X 10.10.5 Flash Version: The confusion is compounded by the 'Update on reload' checkbox remaining in its original unchecked/checked state, whereas it appears that the option is enabled/disabled (or otherwise interrupted) by a another devtools instance.
,
Mar 22 2017
I think there's a question of whether or not this is; a) Expected behaviour (that the option is global), and there's a UI/UX issue making this clear and updating all checkboxes to reflect the global state. b) A bug and/or there's a new requirement to make this tab scoped. From a developers perspective, where you can be working with devtools on multiple sites, I think it needs to be b) tab scoped. The original (I think) Issue 500428 for "Update on reload" discusses global/tab-scope, and my interpretation is that the intention was tab-scope. I'm not sure if this decision was reversed for another reason.
,
Mar 23 2017
,
May 22 2017
Hey, I just reproduced the steps shown above and got exactly the same outcome. In my final year at university we were given the task to build a web application using service workers for offline features. In the development phase this problem confused myself and a few others as the update on reload was behaving in an unexpected way.
,
Oct 12
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jakearchibald@chromium.org
, Mar 21 2017Status: Untriaged (was: Unconfirmed)