Mapping network HTML to file system HTML does not work
Reported by
prashpa...@gmail.com,
Oct 3 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2879.0 Safari/537.36 Steps to reproduce the problem: 1. With Workspace folder already dropped, load up an app. 2. Open index on the sources panel. DevTools suggest to map network resource. 3. Right click on index and try to map it to local index. What is the expected behavior? Mapping is setup for index, together with rest of the assets required by the index. What went wrong? Nothing happens. DevTools keep suggesting to map network resource. Did this work before? Yes Chrome version: 55.0.2879.0 Channel: canary OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 23.0 r0
,
Oct 4 2016
@krajshree Here you go 1. Extract files 2. cd workspace_bug_sample 3. npm i 4. npm start 5. Go to http://localhost:3000 6. Drag workspace_bug_sample folder to sources panel 7. Try mapping (index) to local index.html Works on stable build. Fails on canary build.
,
Oct 5 2016
,
Oct 5 2016
Indeed. On stable, mapping (index) to file system's index.html results in the incorrect mapping (as on screenshot). Chrome Stable accidentally had this working. A workaround in Canary would be navigating page to localhost:3000/index.html. This will make main resource to have a proper name - index.html instead of (index), and mappings will work correctly. We're working on a new mapping system which hopefully will address this and many other problems, stay tuned!
,
Oct 6 2016
@lushnikov The workaround will definitely do for now. Thanks!
,
Oct 7 2016
Thanks for the heads-up, closing this for now
,
Oct 7 2016
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by krajshree@chromium.org
, Oct 4 2016Labels: Needs-Feedback