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

Issue 794184 link

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



Sign in to add a comment

workspace code mapping failure for SAPUI5 based javascript application

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

Platform: <Mac>
Chrome version: <63>

Code is not linked and am no longer to edit code and have it persisted from dev-tools.  We use an extremely elaborate SAPUI5 infrastructure.  When the code is served, a random token is placed in the path for security reasons. The auto mapping is likely tripped up by that.

Is there a way to revert to the old method of mapping?

attached is a screenshot of my server based code tree
File system content.png
25.7 KB View Download

Comment 1 by ernestje...@gmail.com, Dec 12 2017 

server side didn't attach for some reason
server-side-tree.png
59.7 KB View Download

Comment 2 by szymon.k...@gmail.com, Dec 12 2017 

I have noticed the same problem with my Chrome 63.0.3239.84 on Mac. With Chrome Canary  65.0.3292.0 the problem also exists. I haven't found any manual option to map network resource to filesystem resource.

Comment 3 by chenwilliam@chromium.org, Dec 12 2017

Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 4 by lushnikov@chromium.org, Dec 20 2017

Status: WontFix (was: Assigned)
The new workspaces work only with localhost:// domains.
To override resources served from real websites, use the new "network overrides" feature: https://umaar.com/dev-tips/162-network-overrides/
►

Sign in to add a comment