New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 889316 link

Starred by 1 user
Status: WontFix
Owner:
█ lushnikov@chromium.org
Last visit 28 days ago
Closed: Dec 7
Cc:
viswa.karala@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Automatically mapping not working at all

Reported by dcat.des...@gmail.com, Sep 26 
DevTools failed to link network resource to filesystem.

Platform: Win
Chrome version: 69.0.3497.100

What are the details of your project?
- Build System: gulp
- HTTP server: HTTP nginx/apache...

Assets failed to link (or incorrectly linked):
1. All CSS files

Local and network projects has same structure, but files not mapping at all. I'm adding different folders - root, theme, css - just wasting time.

Am i doing something wrong or what?

Screenshot +
chrome_2018-09-26_04-45-13.png
48.1 KB View Download

Comment 1 by viswa.karala@chromium.org, Sep 26

Labels: Needs-Triage-M69

Comment 2 by krajshree@chromium.org, Sep 28

Labels: Triaged-ET
Owner: lushnikov@chromium.org
Assigning it to lushnikov@ from similar issues similar 796368, 794965 and 796251.

Thanks...!!

Comment 3 by viswa.karala@chromium.org, Oct 16

Cc: viswa.karala@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 4 by lushnikov@chromium.org, Dec 7

Status: WontFix (was: Assigned)
Automatic mapping only works for localhost domain; to work with prod websites, use local overrides: https://developers.google.com/web/updates/2018/01/devtools#overrides
►

Sign in to add a comment