Chrome Workspaces broken on Version 49, no breakpoints, source live edit

276 views
Skip to first unread message

Hugh Collins

unread,
Mar 21, 2016, 1:17:07 PM3/21/16
to Google Chrome Developer Tools
This seems similar to other topics posted but I wanted to elaborate on all the critical issues I've found as the new version of workspaces is completely useless in its current state.

Steps to reproduce

  1. Add a folder to workspace
  2. Open a network file
  3. Link the network file to a source file using the right-click context menu
  4. Close all files
  5. Try opening the file using CMD+P and you get the linked workspace file
  6. This is now disjointed from the network file

Symptoms
  • Breakpoints do not work (they appear in the right column but do not get bound and attach to whitespace lines)
  • Debugger statements / manually breaking opens a stack of VM files which are not editable
  • Live editing does not update the code
  • Live editing in the VM files does not affect the workspace files / files on disk
  • No compiling of the workspace files takes place (no syntax errors etc)

I really hope that there is a response to this or similar error reports soon as I'm actually considering using Microsoft Edge to code at this point...
Chrome debugger.png

Pavel Feldman

unread,
Mar 21, 2016, 1:26:59 PM3/21/16
to Google Chrome Developer Tools
This is now fixed and being merged. Here is the bug with the details on how you can fix it manually on your end.

As for the Edge comment, you should use the tool that best serves your needs, so if that is Microsoft Edge at this point, you should migrate!
Pavel

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/42fc59ae-7250-40e3-ab51-943cec6a09c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Shan Jin

unread,
Apr 6, 2016, 2:05:07 AM4/6/16
to Google Chrome Developer Tools
Hi, this is still not fixed. I am not able to 'Map to network resource' for css files. I can click the 'Map...' button but it doesn't do anything. 
Window7, Chrome lastest of 4/5/2016


On Monday, March 21, 2016 at 10:26:59 AM UTC-7, pfeldman wrote:
This is now fixed and being merged. Here is the bug with the details on how you can fix it manually on your end.

As for the Edge comment, you should use the tool that best serves your needs, so if that is Microsoft Edge at this point, you should migrate!
Pavel
On Mon, Mar 21, 2016 at 10:16 AM, Hugh Collins <hu...@codekingdoms.com> wrote:
This seems similar to other topics posted but I wanted to elaborate on all the critical issues I've found as the new version of workspaces is completely useless in its current state.

Steps to reproduce

  1. Add a folder to workspace
  2. Open a network file
  3. Link the network file to a source file using the right-click context menu
  4. Close all files
  5. Try opening the file using CMD+P and you get the linked workspace file
  6. This is now disjointed from the network file

Symptoms
  • Breakpoints do not work (they appear in the right column but do not get bound and attach to whitespace lines)
  • Debugger statements / manually breaking opens a stack of VM files which are not editable
  • Live editing does not update the code
  • Live editing in the VM files does not affect the workspace files / files on disk
  • No compiling of the workspace files takes place (no syntax errors etc)

I really hope that there is a response to this or similar error reports soon as I'm actually considering using Microsoft Edge to code at this point...

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

Andrey Lushnikov

unread,
Apr 6, 2016, 4:51:35 PM4/6/16
to google-chrome-...@googlegroups.com
Could you please file a bug on crbug.com/new and post a link here? We will probably need more details about your case to handle this. 

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/6d86e2c3-c55b-4f66-b5fa-7de479f33fce%40googlegroups.com.

Pavel Feldman

unread,
Apr 6, 2016, 5:36:14 PM4/6/16
to Google Chrome Developer Tools
There is no need to file, please paste your end-to-end scenario with the paths and prefixes into https://bugs.chromium.org/p/chromium/issues/detail?id=595347.

Thanks
Pavel

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CAJZOyhzueGLjbS3UZEayAwzr3VeHLfXm7P1FVpuxxXq3Z_bv%3Dg%40mail.gmail.com.

cavem...@gmail.com

unread,
Apr 15, 2016, 8:43:44 AM4/15/16
to Google Chrome Developer Tools

Are the issues as outlined by the OP resolved in Version 50.0.2661.75 m?  I'm unable to map a local file to a network resource and set break points etc in Version 50.

I was able to revert to version 48 where mapping local javascript resources and using liveedit / debugger works great.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

Pavel Feldman

unread,
Apr 15, 2016, 12:22:35 PM4/15/16
to Google Chrome Developer Tools
Things should have been fixed by now in 49 and 50. Please add your set up details (filesystem paths, serving hostname and prefixes) to the bug and I'll look into it. Please also report what mappings are established and whether they are correct.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/cd2ec0b3-b9f7-4a8e-9765-7522117414cf%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages