Source maps cache not refreshed
Reported by
poremba....@gmail.com,
May 31 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Disable cache on Console -> Network 2. after removing or changing sourcemap file, CHrome does not reflect this and stil used old sourcemap file It does not work for long time. See the issue https://bugs.chromium.org/p/chromium/issues/detail?id=508270 where sergeyv@chromium.org on Nov 25 2015 changed status to "Fixed" but users eports it is still not working. What is the expected behavior? Source mas file should be refreshed after reload What went wrong? Source mas file is not refreshed after reload Did this work before? N/A Chrome version: 58.0.3029.110 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Aug 8 2017
I also observed this behavior in Chrome 60 for Mac as well. Source maps and also the TypeScript files that are mapped to the JavaScript files do not refresh. This behavior is not present in Google Chrome Canary 62.0.3179.0 Chrome version: 60.0.3112.90 Channel: stable OS Version: MacOS Sierra (v10.12.6)
,
Aug 10 2017
Same problemns here using Chrome 60 on windows 10. compiled javascript files are shown correctly in dev tools, but mapped typescript files are not updated even the sourcemap files is. only soution I found so far: close and re-open dev tools to update sourcemaps!
,
Oct 16 2017
,
Dec 8 2017
I believe that this one fixed as well as based on #2 should be fixed in M62. |
|||
►
Sign in to add a comment |
|||
Comment 1 by pfeldman@chromium.org
, Jun 1 2017Status: Assigned (was: Unconfirmed)