Using 'CR only' end of line causes breakpoints's misalignment
Reported by
fa...@bludev.it,
Jun 7 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.62 Safari/537.36 Steps to reproduce the problem: 1. open the attached file (which has lines 8 and 9 with CR instead of CRLF) 2. open devtools and set a breakpoint to row 17 3. reload the page: the debugger stops at line 17 as expected What is the expected behavior? At row 17, all variables should be undefined. What went wrong? Variables w1 and w2 are already assigned, as if the breakpoint were on line 19. The w3 and subsequent are properly unassigned. Did this work before? N/A Chrome version: 67.0.3396.62 Channel: stable OS Version: 10.0 Flash Version:
,
Jun 8 2018
,
Jun 8 2018
fabio@ Thanks for the issue. Tested this issue on Windows 10 on the reported version 67.0.3396.62 and the latest Canary 69.0.3452.0 by following the below steps. 1. Launched Chrome and opened the given html file. 2. opened Devtools -> Sources -> test.html and set breakpoint to line no. 17 and reloaded the page. 3. The debugger stops at line 17 and can see the values w1 = 0; w2 = "";w3 = false; Attached is the screen cast for reference. Request you to check and confirm if this is the issue seen and if anything is missed from our end in triaging the issue. Thanks..
,
Jun 8 2018
Yes, perfect! Thanks
,
Jun 8 2018
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
,
Jun 11 2018
Able to reproduce the issue on reported chrome version stable 67.0.3396.62 and on latest chrome 69.0.3452.0 using Linux Ubuntu 17.10,Windows 10 & Mac 10.13.3. Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. Thanks!
,
Jun 11 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by fa...@bludev.it
, Jun 7 2018370 bytes
370 bytes View Download