"Disable cache (while devtools is open)" option doesn't affect audioWorklet modules
Reported by
nicolas....@gmail.com,
Sep 5
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36 Steps to reproduce the problem: 1. Open devtools and enable the "disable cache option" 2. Open index.html file from the included zip file (using a webserver) 4. Make some change to the mod-processor.js file, insert a console.log for example 5. Reload the page What is the expected behavior? The mod-processor.js file should be reloaded. What went wrong? The previous cached version is used instead. Did this work before? N/A Chrome version: 69.0.3497.81 Channel: stable OS Version: OS X 10.12.6 Flash Version: Note: the file must be opened from a webserver otherwise Chrome's policy will block some requests I'm not sure but I think this used to work in Chrome 68.
,
Sep 5
I downloaded Chrome 68.0.3440.84 and can confirm the problem isn't there: reloading the page with devtools open correctly reload the mod-processor.js file.
,
Sep 5
,
Sep 13
Unable to reproduce the issue on Mac using chrome reported version-69.0.3497.81 as per C#0. mod-processor.js file is getting reloaded successfully with new modifications in .js file (we can see in console).
Steps:
-----
1.Run python -m SimpleHTTPServer 8000 from terminal from downloaded path
2.Launch chrome
3.Type localhost:8000/index.html
4.Open dev tools
5.Goto Network tab & check disable cache check box
6.Go to sources-> select mod.processor.js & insert command as console.log('test mac')
7.Goto console and observed test mac text
Same behavior is seen on 68.0.3440.84 too. Please find the attached screencast for reference & let us know if we miss any steps from our end.
Thanks..!
,
Sep 13
The problem I was referring to is when you edit the file from *outside* Chrome (like VSCode, nano, any editor), not when editing the file from Chrome. In that case, reloading the page after modifying the file that's use as audioWorkletNode module isn't refreshed. In previous Chrome release it was refreshed correctly.
,
Sep 13
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 13
Here is a video: https://youtu.be/0F0KJ35v9ho I first load the page, then add a "console.log('hey');", reload the page and the console.log doesn't appear. If I open the mod-processor.js file by typing its url in the address field, it seems it refreshes the cache, so reloading the page will then use the updated version.
,
Oct 8
,
Nov 9
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by nicolas....@gmail.com
, Sep 51.3 KB
1.3 KB Download