Possible alternative workaround for Web Control Reload Issue
Posted: Sat Mar 09, 2019 6:19 pm
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
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