BP sliding - class scope change
Reported by
sandroto...@googlemail.com,
Nov 5
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0 Steps to reproduce the problem: 1. Open min.html (see attached) 2. Set BPs as indicated in devtools.mkv What is the expected behavior? The scope of the BP should remain the same, whether the BP was created in the line or was slid there. What went wrong? The scope changes depending on BP creation method. Did this work before? N/A Chrome version: 70.0.3538.77 Channel: stable OS Version: Arch Linux Flash Version: n/a
,
Nov 12
,
Nov 19
Thanks for the issue... Tried to reproduce the issue on reported chrome 70.0.3538.77 using Ubuntu 17.10. Attaching screenshot for reference. Steps: ----- 1. Launched reported chrome 2. Downloaded and kept in one folder the given file 3. Opened min.js file and Opened Dev tools > Sources 4. setted breakpoints as per given screencast As we have not seen local on right side in sources @Repoter: Could you please check the attached screenshot and let us know if anything missed from our end. Thanks..!
,
Nov 19
Please retry the steps using the provided min.html file, if you open min.js directly the debugger behavior changes.
,
Nov 19
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 20
Tried testing the issue on reported chrome version #70.0.3538.77 using Ubuntu 17.10 by following below steps. Steps: ====== 1.Launched chrome. 2.Opened "min.html". 3.Under Devtools->Sources, opened "min.js". 4.The breakpoint had been set as per screencast. 5.Observed that in both cases of creating the breakpoint and removing the breakpoint the "Return value: undefined this: C" has been displayed. Attached screencast for reference. @reporter: Could you please review attached screencast and let us know if anything is being missed here. Thanks.!
,
Nov 20
The "this: C" disappears from the scope when the breakpoint is moved to the line. I.e., create the breakpoint in line 1 (at the //comment) and reload the page. Then, the scope should change.
,
Nov 20
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 26
Tried testing the issue on reported chrome version #70.0.3538.77 using Ubuntu 17.10 by following steps as per comment#0 and comment#7. Unable to set the breakpoint in line 1(at the //comment). Attached screencast for reference, @reporter: Could you please review attached screencast and let us know if anything is being missed here. Thanks.!
,
Nov 26
You first need to remove the breakpoint from line 2, then create on in line 1. It will be moved to line 2. Then, reload the page. This should trigger the bug.
,
Nov 26
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 5
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by vamshi.kommuri@chromium.org
, Nov 5