Removing the breakpoint while setting up a condition breaks the the chrome dev tools
Reported by
bu...@systemonesoftware.com,
Jan 16
(6 days ago)
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce the problem: 1. Create a simple HTML page with some javascript in it. I used a local file called page.html with the content listed at the bottom. 2. Open this page in Chrome with dev tools open. 3. Open this page.html in the sources tab 4. Set a normal breakpoint on the first console.log statement by clicking on the line number next to the statement 5. Right click this blue breakpoint, click on "edit breakpoint" 6. It will ask for a condition. Instead, click on the blue breakpoint icon again. <html> <head> <script> console.log(1); console.log(1); </script> </head> <body></body> </html> What is the expected behavior? The breakpoint will be removed and the window asking you for a condition should disappear. What went wrong? The window that asks you to set a condition will remain open. The line you set a breakpoint for will appear above and below this window asking for a condition. If you try to mess around by setting more breakpoints, it will behave very strange and the window won't update anymore. Eventually this source tab will turn blank. If the dev tools is docked at the bottom and you try to resize it, the view port won't adjust properly. I attached a gif that clearly shows the problem in action. This was in incognito mode with all extensions disabled, although the problem also happens outside of incognito with my extensions. Did this work before? N/A Chrome version: 71.0.3578.98 Channel: stable OS Version: 10.0 Flash Version:
,
Jan 18
(5 days ago)
|
||
►
Sign in to add a comment |
||
Comment 1 by viswa.karala@chromium.org
, Jan 17 (6 days ago)