Behavior of BPs inconsitent for IFs
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 "example.html" (see attached) 2. Set BPs as shown in "devtools.mkv" (see attached) What is the expected behavior? The BP in line 6 and 14 should be set at the beginning of the if-statement. What went wrong? The BP is set inside the if-body (in the "true"-case) or completely moved past the if (in the "false"-case). This is inconsistent with the behavior of other if-conditions (even if they are trivially identical to the aforementioned cases). Did this work before? N/A Chrome version: 67.0.3396.99 Channel: stable OS Version: Arch Linux x64 Flash Version: n/a Probably related to some sort of static analysis/optimization of the JS? However it should still be possible to set a BP at these locations, as they are statements that are executed (at least to the web-developer).
,
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 13
,
Sep 21
It works as intended, we allow to set breakpoints only at locations where something more then nop happens. We may consider out heuristic in a future or provide better UX feedback to describe why breakpoint was shifted. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by susan.boorgula@chromium.org
, Jul 12