Issue metadata
Sign in to add a comment
|
Sources/workspaces not working
Reported by
sam.stam...@gmail.com,
Feb 11 2017
|
||||||||||||||||||||||||
Issue description
Chrome Version : 56.0.2924.87
OS Version: 10.0
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
Please see https://groups.google.com/forum/#!topic/google-chrome-developer-tools/YYGgABJ-kuU for details including steps to reproduce this problem.
UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
,
Feb 14 2017
,
Feb 17 2017
Thanks for the report. I'm not sure how to reproduce the screenshot, though. The "Recording_20170208_0839.mht" file doesn't have any references to "base.css" or "style.css". - Have you tried to link your files on the latest Chrome Canary? - Have you tried on a new, clean profile?
,
Feb 17 2017
I'm a newbie. Please define Chrome Canary. I'm using Chrome. Also, what do you mean by a new, clean profile?
,
Feb 17 2017
Hi Sam, Chrome Canary is the latest-and-greatest build of Chrome, updated daily: https://www.google.com/chrome/browser/canary.html From your report, I can't load the recording. Could you attach it to the bug? Also, the screenshot does not clarify things much. A step-by-step scenario with (prefferably) link to the repository would help a lot!
,
Feb 18 2017
I downloaded Chrome Canary. Results are similar except I now see a message "no files found" when I try to map. Attached is a Word file where I copied all the steps I went through. You may have to close this problem since you won't be able to mimic what I did exactly since I have the problem with a local web site I'm working on. Also, I don't need this functionality at this time, it would be nice to have it work if I need it sometime in the future.
,
Feb 21 2017
Sam, The problem in your case is in query parameters of style.css file. This, however, was solved under the "Persistence2.0" experiment. Please, give it a shot. To enable experiment: 1. Run Chrome Canary 2. Navigate to about:flags and enable "Developer Tools experiments" flag. 3. Restart chrome 4. Open Developer Tools 5. Goto DevTools settings (e.g. via hitting F1) 6. Navigate to "experiments" tab in DevTools settings 7. Enable the "Persistence2.0" experiment. 8. Re-open devtools. With this experiment enabled, all the mappings will be inferred automatically. When a mapping is established, your resource will be marked with a green bubble (like on a screenshot).
,
Mar 3 2017
Sorry I took so long to respond. Life gets crazy sometimes! Will this fix be rolled into the regular edition of Chrome? If so, when?
,
Mar 3 2017
Thank you for providing more feedback. Adding requester "luoe@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 6 2017
@Sam, if the experiment proves useful, it will. But we're still experimenting. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Feb 13 2017