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

Issue 805501 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Last visit 28 days ago
Closed: Dec 8
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Workspaces ignores CSS file but not JS

Reported by lord.c...@gmail.com, Jan 24 2018

Issue description

DevTools failed to link network resource to filesystem after I add the root folder to the workspace.
Playing around with the content, the JS gets updated on disk but not the CSS file. 
Adding the subfolder (dynoboo) to the workspace cancels all mappings.
Right clicking the CSS yields no option to map it manually.

Platform: Win
Chrome version: 63.0.3239.132

What are the details of your project?
./dynobootemplate.html
./dynoboo/main.js
./dynoboo/main.css

Assets failed to link (or incorrectly linked):
1. main.css
 
moody.jpg
141 KB View Download
Labels: Needs-Triage-M63
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Had you previously been editing the css file in the style sidebar? The content might not match anymore.

Comment 3 by lord.c...@gmail.com, Jan 26 2018

No. But two things did happen.

First, I moved these 3 files over to a new location, removed the old workspace path and added the new one before this issue/impatience happened.
Second, after working manually for about 10 minutes, it linked to the CSS.

I'm not sure if I was supposed to be more patient and simply wait longer.
Regardless, it works now.
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