Chrome Devtools job display no longer works

Question

This was used to work in charm, and I probably used the same hardware / software a dozen times in the past, but now it fails:

The necessary permissions for in-place editing, because I can edit the file in Devtools, if I open it directly from the local workspace in the sources tab, edit and save it, but this, of course, is no better than using any other IDE. since I don’t see and immediately save my changes, as I used to:

Without the LESS / SASS / Taskrunner skill, just CSS files.

I looked at Sawbuck, Devtools on Devtools and see no errors.

I completely disabled the firewall.

I use Windows 7, Chrome 56 (and tried Canary, 58, too), and the server file system is mounted as a network drive, on Z :.

One of the weird things is how the display of the workspace seems to process the files as directories after I set up the resource link by right-clicking on the remote resource and selecting "Map for file system ..." or a local resource and the choice of "Map to network resource ...", but it could always be so, and I never noticed - in any case, I also manually added the mapping of the parent directory and the root directory of the site, but the result is the same; no permanent changes.

I'm usually too proud to ask a question about something like this, and spend years trying to figure it out on my own, but I feel like I hit too hard on a brick wall. I would appreciate any pointers if you had a similar experience.

Answer 1

It seems that prior to the cache delete request line that WordPress adds,

You can see this in my screenshot ?ver=4.7.2

Clearly, I had to use this DevTools Workspace feature before integrating into Wordpress. Here is the relevant Chromium bug report .

Now by adding this to functions.php in WordPress to remove the redundant cache suffix, I can re-enable persistent changes:

 function fj_remove_version( $url ) { return remove_query_arg( 'ver', $url ); } add_filter( 'style_loader_src', 'fj_remove_version' ); 

In the future, it looks like Persistence 2.0 , recommended at the end of the bug report. Now it can be included as a Chrome DevTool experiment .