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

Issue 798108 link

Starred by 3 users
Status: Archived
Owner:
█ lushnikov@chromium.org
Last visit 28 days ago
Closed: Dec 8
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

DevTools: Need indication when mapping failed due to different content

Reported by lukeriss...@gmail.com, Dec 29 2017 
DevTools failed to link network resource to filesystem.

Platform: Windows 7
Chrome version: 63.0.3239.84 (Official Build) (64-bit)

What are the details of your project?
- Source code (if any): local Flask site; static files are simple flat folder, no cache-breakers in link tags, etc.
- Build System: none
- HTTP server: Flask dev server

Assets failed to link (or incorrectly linked):
1. /static/css/screen.css   ->   /(mapped folder)/static/css/screen.css

See attached screenshot.
FailedMapping.png
48.8 KB View Download

Comment 1 by lukeriss...@gmail.com, Dec 29 2017 

Update on this; I did a full-cache refresh on my local dev site (Ctrl-F5) and it picked up the mapping correctly again. Cache for static resources on my dev server is set with max-age 0, so seems like Chrome is holding onto files too long then missing the mapping somehow.

Comment 2 by dgozman@chromium.org, Dec 31 2017

Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Summary: DevTools: Need indication when mapping failed due to different content (was: PLEASE allow manual mappings again! Or let us downgrade to Chrome 62. This )
Perhaps, we should indicate why the mapping has failed (in this case - content mismatch) and suggest the solution. This way developers are not confused, but rather informed.

Comment 3 by lukeriss...@gmail.com, Dec 31 2017 

Cool, yeah some indication of failure reason would be helpful. 

One other update, I actually did not have the cache max-age=0 response header set in my code for this site like I thought I did. So Chrome was obeying cache rules correctly, although the lack of reason for the failed mapping was still confusing.

Comment 4 by lushnikov@chromium.org, Dec 8

Status: Archived (was: Assigned)
Workspaces 2.0 is imperfect and there's no feasible way to make it work for everybody. Archiving since we currently don't have resources to allocate towards improving Workspaces story.
►

Sign in to add a comment