Breakpoints in Developer Tools seem broken if script path has lowercase drive letter on Windows
Reported by
vsemozhe...@gmail.com,
Mar 10 2018
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3367.0 Safari/537.36 Steps to reproduce the problem: See the first and the second comments in https://github.com/nodejs/node/issues/19273 What is the expected behavior? Breakpoints are not dependent on letter case of script path in a case-insensitive OS like Windows What went wrong? Breakpoints are dependent on letter case of script path in a case-insensitive OS like Windows Did this work before? N/A Chrome version: 67.0.3367.0 Channel: canary OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: 29.0.0.117
,
Mar 15 2018
Pretty sure this is because the script name no longer matches. Probably observable on Chrome when running local files on Windows too. Since Windows paths are case insensitive, I think this might affect more than just the drive letter.
,
May 2 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by caseq@chromium.org
, Mar 11 2018Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)