Issue metadata
Sign in to add a comment
|
Breakpoints in DevEditor are not set until page refresh
Reported by
jarro...@gmail.com,
Dec 10 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2922.1 Safari/537.36 Steps to reproduce the problem: 1. Set a breakpoint 2. Execute code which should trigger breakpoint What is the expected behavior? JavaScript execution stops in the breakponit line. What went wrong? It never stops until next page reload. Did this work before? N/A Chrome version: 56.0.2922.1 Channel: dev OS Version: 56.0.2922.1 Flash Version: Shockwave Flash 24.0 r0 It started a few weeks ago. It's annoying enough to file an issue report :) I think that in previous Chrome version it was working properly. Now I have to refresh the page each time I want to use a breakpoint.
,
Dec 12 2016
Thanks for submitting a bug report. Can you provide a simple repro case? You can use https://jsfiddle.net/ or any other snippet site. Also, if you can provide a video snippet / animated GIF, that would be really helpful. Thanks!
,
Dec 12 2016
,
Dec 12 2016
It was broken and then fixed around one week ago with CL [1]. Could you confirm that you can reproduce it with last dev version (56.0.2924.14)? [1] https://codereview.chromium.org/2540943002/
,
Dec 12 2016
I'm not sure how I could use jsfiddle to show how to set up a breakpoint :) But it made me thinking about use case and I may have some additional info. I've recorded a video: https://drive.google.com/file/d/0Bzpy9PK_RiBOeXhCZDNQMnRTX28/view?usp=sharing In the video, I'm refreshing the page, then after some data used to build the view were loaded then I'm setting a breakpoint to a function that is handling the 'input' event on a text field. When changing the value nothing happens. After another page refresh, the breakpoint started working as expected. Now, I started looking for an example script where I can provide a case and I noticed one thing. When the breakpoint was set on a function that is happening on mouse input (click) it worked. On the same page, when the breakpoint was set to user keyboard input (key down) it didn't work. Hope it helps. But if it still hard to reproduce the issue I can try to provide you with another example.
,
Dec 12 2016
I can confirm that it is working in Chromium build revision: 437929 (Version 57.0.2950.0) Not sure how to get the 56.0.2924.14 version :)
,
Dec 13 2016
jarrodek@ - Thanks for filing this issue...!! The builds can be downloaded using the following URL: https://www.chromium.org/getting-involved/dev-channel Please try testing this issue using the latest dev channel. A manual repro test case with a sample URL will be more appreciated. This will help us in triaging the issue further. Thanks...!!
,
Dec 14 2016
Sounds like this is fixed on ToT. Jarrdeck, can you try out dev-channel and see if you can repro? thanks
,
Dec 14 2016
Hi, I've tested it in latest dev and it is working as expected. The bug is no longer there. This issue report can be closed.
,
Dec 14 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Dec 12 2016