Setting breakpoints, while local files are mapped, fail to work correctly.
Reported by
tbmstech...@gmail.com,
Jun 9 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: Open up a page with some file.js loaded in via a script tag. Map the file.js to the local file.js. Select the remote file in the sources tab. These things should now be linked. Set a breakpoint by selecting the remote file and placing a breakpoint somewhere. Set a breakpoint on the local file. Notice the breakpoint you set on the remote file doesnt exist in the local file. Now when the application lands on the breakpoint, you stop on the remote file What is the expected behavior? When I link files, map local to remove I expect that my remote files will be overridden by the local ones AT ALL COSTS. What went wrong? The remote file open up when I have specifically mapped a local file to replace it. So edits etc, appear to save and then dont. Did this work before? N/A Chrome version: 58.0.3029.110 Channel: n/a OS Version: 10.0 Flash Version: This is so obvious. How could this get past testing??? Its broken.
,
Jun 9 2017
I forgot to mention that local breakpoints NEVER work. You can set them, but they never work. So not only do edits in the sources tab not get reflected in the local files, if you happen to open the remote one and make edits, and hit ctrl+s it looks like it saved but doesnt. So you can end up with edits all over while debugging and then loose them all when you refresh the page. You need to find you local files to do the edits in...and also if you set breakpoints you cant set them in the local file you have to set them remotely. Then fix you code by selecting the local file, finding the line you were on and making an edit. There is no mapping, not in any sense. Local files should REPLACE remote ones. I dont want to see the remote file anywhere in the sources tab because the sources should reflect the sources used.
,
Jun 19 2017
,
Jun 22 2017
,
Jul 5 2017
There was a major refactor of workspaces recently. Can you try this on Canary and see if this issue still exists? Thanks!
,
Jul 5 2017
,
Jul 5 2017
I think exactly this problem was fixed recently via https://codereview.chromium.org/2886643002
,
Dec 6 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 Deleted