Inconsistent behavior of BPs returned "getPossibleBreakpoints"/ in the GUI for functions
Reported by
sandroto...@googlemail.com,
Jul 12
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 Steps to reproduce the problem: 1. Open file "example.html" (see attached) 2. Set BPs as shown in "devtools.mkv" (see attached) What is the expected behavior? The BP in line 13, column 23 should not be suggested. This would then be consistent with the other functions. What went wrong? The BP in line 13, column 23 is suggested. When it is selected, the BP is moved to the function body (consistent with the behavior of other functions). This can also be reproduced via the DevTools API (see attached set_breakpoint.ts, requires node.js and chrome-remote-interface). When a BP is set at the location returned by getPossibleBreakpoints (at the "function" node), the BP is moved to inside the function. However, if the BP is set to one column before the "function" node, the BP is moved to the "function" node, not inside its body. The Debugger also stops at this location when hitting the BP (this cannot be reproduced in the GUI because setting BPs at arbitrary locations is not possible). Did this work before? N/A Chrome version: 67.0.3396.99 Channel: stable OS Version: Arch Linux x64 Flash Version: n/a
,
Jul 13
Thanks for filing the issue! This issue seems to be similar to Issue: 862980 , hence With reference to that issue, CC'ing the Owner(kozy@chromium.org) for further inputs on this issue. Thanks!
,
Jul 20
Gentle ping ------------ Requesting kozy@ to give a confirmation as per the comment#2 if this issue is similar to that of the above mentioned issue(C#2). Thanks!
,
Jul 25
As per comment #2 and #3, adding 'TE-NeedsTriageHelp' label and requesting the appropriate team to look into the issue and help in further triaging. Thanks.
,
Aug 18
,
Sep 24
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by susan.boorgula@chromium.org
, Jul 12