Issue metadata
Sign in to add a comment
|
Workspaces are broken after version 63 release of Workspaces 2.0
Reported by
r...@vicesoftware.com,
Feb 26 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Steps to reproduce the problem: 1. Run and open local site, I'm using a create-react-app based site using npm start command 2. Open devtools sources 3. Click file system 4. Add the local directory with your sites source in them 5. Open a JS file in sources using command+p 5. Expand the "map workspace resource..." popup 6. Click "Establish mapping now..." 7. Pick the local version of your file that is in your local workspace that you added above What is the expected behavior? Mapping is established and I can (1) set breakpoints in workspace files and hit them (2) I can edit workspace files and then see those changes after refreshing What went wrong? Mapping is not established and I can't (1) set breakpoints in workspace files and hit them (2) I can edit workspace files and then see those changes after refreshing Did this work before? Yes 62 it was broken with 63 release and is still broken in 64 Chrome version: 64.0.3282.167 Channel: n/a OS Version: 10.0 Flash Version: "Help me obi wan you're my only hope"
,
Feb 27 2018
,
Feb 27 2018
@lushnikov: Could you please confirm whether this issue is similar to that of 796368, 794965 and 796251. Note: Removing Needs-Bisect label, please add it back if required. Thanks...!!
,
Feb 27 2018
vamshi.kommuri@chromium.org this does look similar. However, some of those issues were linking to duplicates that didn't seem similar and referenced work around that didn't seem relevant to the concern. Do you know if this issue is being tracked for resolution in the related tickets?
,
Dec 19
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Feb 27 2018