Issue metadata
Sign in to add a comment
|
PLEASE BRING BACK THE OPTION TO MANUALLY LINK RESOURCES
Reported by
manth...@gmail.com,
Dec 19 2017
|
||||||||||||||||||||||||
Issue descriptionDevTools failed to link network resource to filesystem. PLEASE BRING BACK THE OPTION TO MANUALLY LINK RESOURCES I don't think there is any heuristic that will make this automation possible, or correct for all cases. For example, visiting a URL without the /index.html will not find mappings, whereas appending the /index.html sometimes improves the results. This is very brittle. Please bring back the option to manually map to FS/network resource. Source file names change according to maps/transpilers/build tools. Platform: <Linux/Win/Mac> Chrome version: <your chrome version> What are the details of your project? - Source code (if any): http://github.com/example/example - Build System: gulp/grunt/webpack/rollup/... - HTTP server: node HTTP/nginx/apache... Assets failed to link (or incorrectly linked): 1. 2. 3. If possible, please attach a screenshot of network sources navigator which should show which resources failed to map
,
Apr 18 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Dec 20 2017Labels: Needs-Milestone Triaged-ET
Mergedinto: 794965
Status: Duplicate (was: Unconfirmed)