@lushnikov: Could you please confirm whether this issue is similar to that of 796368, 794965 and 796251.

Thanks!

Hi guys,

I went thru the tickets you listed here and I can say they are similar issues but not the same.


* 796368: Is trying to map the assets, but, he is loading a different URL (/ and /index.html)
* 794965: This is a completely different issue, there is a mapping done and it is loading the files from the file system.
* 796251: Looks similar, although they are talking about TypeScript files not mapped, also, on the provided screenshot, I noticed they are getting the option to establish the mapping to the filesystem (maybe that screenshot is for a previous version of Chrome).

Some extra information related to the project I am working on:
* The resources I am trying to map are plain CSS files (no transpiler is used, so there aren't any source maps)
* The URL I am accessing is a network resource eg.: stage.example.com
* I have attached the folder with the matching URI to the one used on the web page.

Hi guys,

I don't know if you did something to this.

I'm now using Chrome Version 69.0.3497.100. I can see the bindings to the file system are working again.

The problem may be produced the way my project is configured.

The project I'm working on is big and it is running inside a virtual machine. I'm accessing the files through an NFS mount, this may be causing Chrome to take a long time to index and load the files.

I haven't changed anything else in my current environment, but the file linking suddenly began working.

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.