Issue metadata
Sign in to add a comment
|
Chrome Developer Tools Deactivate Breakpoints state not persisted after reloading page
Reported by
intrama...@gmail.com,
Aug 1 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36 Steps to reproduce the problem: 1. Deactivate breakpoints (Ctrl+F8) 2. Reload page 3. Breakpoints are active again What is the expected behavior? Many moons ago, the state is remembered correctly after reloading page, e.g. if breakpoints are deactivated (Ctrl+F8), it will stay as deactivated after reloading page. However current version of Chrome v60.xx (maybe v56 and above?, not sure when it starts) re-activate breakpoints after reloading page. What went wrong? Breakpoints are active again after reloading page. Did this work before? Yes not sure...before v56? Chrome version: 60.0.3112.78 Channel: stable OS Version: 6.2 (Windows 8) Flash Version:
,
Aug 8 2017
This starts working again to my delight. it might be a Chrome restart or computer restart that did it.
,
Oct 13 2017
Thanks for report, feel free to file an issue if the bug is still reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by eostroukhov@chromium.org
, Aug 1 2017Status: Assigned (was: Unconfirmed)