After bumping the GitHub bug about this issue, I got to thinking about it more, did some reading, and I wanted to post my conclusion for anyone who may find it useful since I haven't seen it previously suggested.
One of the Chromium project's current initiatives is to overhaul the browser's caching system. After some testing, it does seem that enabling the experimental flag for this implementation environmentally resolves Web Control's looping reload issue.
Version 72.0.3626.121 (Official Build) (64-bit)
chrome://flags/#enable-simple-cache-backend
Possible alternative workaround for Web Control Reload Issue
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 117
- Joined: Mon Mar 16, 2009 3:06 am
-
- Posts: 117
- Joined: Mon Mar 16, 2009 3:06 am
Re: Possible alternative workaround for Web Control Reload I
Actually, it turns out that the setting itself doesn't resolve the issue, but toggling it does since it does a sort of reset on the cache. That's still rather nice though, because it means you can quickly clear the issue without having to dump your whole cache or use incognito instances.
[img 468x60]https://folding.extremeoverclocking.com ... p?u=679048[/img]