Local Overrides Not Working

[Adnan Fida]

Tried both Chrome 67  (67.0.3396.99 (Official Build) (64-bit)) and Canary 69 (69.0.3484.0 (Official Build) canary (64-bit)) on MacOS 10.11.6. 

To reproduce:

1. Visit https://www.york.ac.uk/teaching/cws/wws/webpage1.html
   
2. Configure (enable) Local Overrides
3. From DevTools > Network panel, right click on webpage1.html and select 'Save for overrides' (only showing up for Canary) or open the file in Source panel
4. Edit HTML in Sources panel and save
5. Notice the Network panel showing a warning that Request maybe overwritten (good)
6. Hit refresh and the page is loaded from the source while ignoring the override

What am I missing? 

Thanks.

[Kerry Johnson]

Can confirm.  Local Overrides is a new feature and while it works, it's great, but I've also experience times where it doesn't apply.

[Andrew Kean Guan]

Not working on Mac and Windows.  Version 68.

[Zoltan Kochan]

For me it works ~9 times from 10 but sometimes it doesn't. I use fresh incognito window every time. Windows 10. Chrome 68.0.3440.106 (Official Build) (64-bit)

[Bone Mr]

same, I override try in incognito mode, it works.

[SikoSoft]

Doesn't work for me either.

One out of maybe 200 attempts I saw some effect, but every attempt since then it has not worked.

68.0.3440.106 (Official Build) (64-bit)

[Daniel Busłowicz]

Same thing here, Chrome 69.0.3497.100 (Official Build) (64-bit) on Windows 10 Pro, local overrides are ignored.

[javi garcia]

I tried to turn off all the plugins and same result.

finally overrides worked for me with a clean Canary installation

[stefan...@gmail.com]

 OVERRIDE is a fabulous feature. I love it.  

It works well on my latest Chrome App, (desktop Windows), 

BUT: The HTML changes applied inside the sources TAB for the HTML-Document itself will  NOT persist! 

This is an unexpected behaviour. And it is new, it used to work.

Chrome Dev Tools - latest version - Windows operating machine  

[Ben Wheeler]

I also couldn't get Overrides to work -- the changes would persist, but they wouldn't actually be applied
.

The problem turned out to be double slashes in the file's URL -- Chrome didn't realize that `http://domain.ext/path/to/my//file.js` matched its local `domain.ext`/`path`/`to`/`my`/`file.js .