Issue metadata
Sign in to add a comment
|
'debugger;' added to javascript doesn't break
Reported by
davidmax...@gmail.com,
Jun 29 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. add a 'debugger;' statement to code 2. open dev tools 3. run code What is the expected behavior? I expect the debugger to break on the 'debugger;' What went wrong? It doesn't break...it seems to kind of stutter (a visual flash or something), but doesn't stop. Did this work before? Yes don't know Chrome version: 59.0.3071.115 Channel: stable OS Version: 10.0 Flash Version: Other people on the polymer slack channel have seen this too, and one told me that a workaround is to add two 'debugger;' statements in succession, and that does indeed work - ie: debugger; debugger;
,
Jul 5 2017
,
Jul 5 2017
I definitely need a sample test here, please provide more details, otherwise it's mostly impossible to debug this issue. We actually fixed similar issue recently and if you can try your repro with latest Chrome Canary - it would be great.
,
Jul 5 2017
Unfortunately, it isn't reliably reproducible. Today, I managed to get just a single debugger; statement to break ok, and I notice I'm still using the same version as when I opened this case. Do you have a reference to the similar issue? Perhaps I can recognise what is causing that.
,
Oct 16 2017
,
Dec 12 2017
I can not reproduce this one. If it still reproducible feel free to reopen it! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by sandeepkumars@chromium.org
, Jun 30 2017