DevTools: UI solution for breakpoint and blackboxing
Reported by
roblour...@gmail.com,
Feb 14 2018
|
||||
Issue descriptionChrome Version : 64.0.3282.140 OS Version: OS X 10.13.2 URLs (if applicable) : What steps will reproduce the problem? 1. Mark a script as blackboxed 2. Set a breakpoint in the script 3. Hit the breakpoint 4. Step What is the expected result? I should step to the next line of this blackboxed script What happens instead of that? Execution continues out of the blackboxed script Previously (not sure which Chrome version but I see it in Node 7.10 at least) if I hit a breakpoint in a blackboxed script, then stepped, I would be able to step line by line through that script. I like this behavior because if I hit a breakpoint in a script, then I intend to debug that script. So I'm not sure whether this is a design change or a regression.
,
Feb 14 2018
Unable to reproduce this issue on reported version 64.0.3282.140 using Mac 10.13.3 with below steps. 1. Launched chorme://version and opened devtools sources tab. 2. Blackboxed script, set breakpoint, now clicked on step funnction -- observed step to next line. Attaching screencast for reference. @Reporter: Please check the video and let us know if we miss anything? If possible please guide us with a video on how to reproduce this issue? This would help in better triaging of the issue. Thanks!
,
Mar 12 2018
This is intended behavior. Aleksey, we should make the UI suggest to unblackbox this file (temporary?) for stepping.
,
Sep 25
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ajha@chromium.org
, Feb 14 2018