Nested function, Object destructuring - Local variable disappears from scope
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 2. Set BPs as shown in devtools.mkv What is the expected behavior? The local variable "y" should exist in both cases. What went wrong? If the variable is used in a nested function, it disappears from the scope. Did this work before? N/A Chrome version: 70.0.3538.77 Channel: stable OS Version: Arch Linux Flash Version: n/a The outer functions have to generators because a "normal" function does no allow a BP at this location. Not sure if the behavior is otherwise related to generators.
,
Nov 12
,
Nov 13
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. Downloaded both files (min.html and min.js) and navigated to devtools->Console. 3. Clicked on the 1st line and 5th line and set the breakpoints for both lines. 4. Observed that the parameters of the function test and function test1 are not getting selected. Attached screencast for reference. @Reporter: Could you please check the attached screencast and please let us know if anything missed from our end and verify this issue on latest chrome " https://www.chromium.org/getting-involved/dev-channel ". Let us know whether the issue still persists Thanks..!
,
Nov 14
I have not tested this on latest stable, however I verified that the bug still exists in version 70.0.3538.102. Also, you need to load the script via the min.html file, accessing the .js file directly doesn't work.
,
Nov 14
I mean latest dev, of course.
,
Nov 14
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 as per comment#4, able to reproduce the issue on reported chrome version # 70.0.3538.77, latest stable #70.0.3538.110 and latest chrome #72.0.3616.0 using Ubuntu 17.10. While testing the issue on chrome version #60.0.3112.78, found a different behavior that the local variable "y" does not exist in both the cases. @reporter: Could you please confirm if this behavior can be considered as bad behavior. Thanks.!
,
Nov 21
As you mentioned, you manged to reproduce the inconsistent behavior, which I consider to be a bug. Also, as you showed, the behavior is different/correct(?) in version #60.0.3112.78, so I would consider this a regression.
,
Nov 21
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 22
As per comment#9, it is not clear that the behavior of the chrome version #60.0.3112.78 should be as good or bad. @reporter: Could you please confirm how the behavior should be considered so that it would be really helpful for further triaging of the issue. Thanks.!
,
Nov 26
I would consider the behavior as bad. I would expect that the variable y is present at the pause locations, as it would be useful to see the value which is passed as an argument.
,
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
,
Nov 27
Able to reproduce the issue on reported chrome version # 70.0.3538.77, latest stable #70.0.3538.110 and latest chrome #72.0.3622.0 using Ubuntu 17.10, Windows 10 and Mac 10.14.1. The issue is seen from old M-60 builds(#60.0.3112.78). This is a non-regression issue hence, marking it as untriaged and requesting someone from the dev team to look into the issue. Thanks.!
,
Dec 5
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by vamshi.kommuri@chromium.org
, Nov 5