Devtools > Application > CacheStorage > (check a request) Response > Preview; Maybe show wrong content
Reported by
hughfeng...@gmail.com,
Dec 26
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce the problem: 1. Open url: https://www.google.com/ and Console panel 2. Excute code in Console panel. ``` t = await caches.open('test') await t.put('timestamp', new Response(Date.now())) t = await caches.open('test1') await t.put('timestamp', new Response(Date.now())) console.log(await (await t.match('timestamp')).text()) ``` 3. Check `cacheKey:test1; request:timestamp`, compare Preview Panel () and Console.log What is the expected behavior? Preview Panel content and Console.log is equal. What went wrong? Preview Panel content and Console.log isn't equal. Did this work before? N/A Chrome version: 71.0.3578.98 Channel: stable OS Version: OS X 10.13.4 Flash Version: cacheKey:test and cacheKey:test1 timestamp content always same.
,
Dec 27
Thanks for filing the issue.. Able to reproduce the issue on reported chrome version 71.0.3578.98 also on latest chrome 73.0.3652.0 using Mac 10.14.0, Ubuntu 17.10 and Windows 10. Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. Thanks..!
,
Dec 27
++ Correction: From M-60 to M-62 seen Uncaught SyntaxError: Unexpected identifier and from M-63 to M-73 observed the issue. Thanks..!
,
Jan 2
Some other observations:
* Its not dependent on the name of the Cache objects. I used caches.open("foo") and also got the same result.
* Deleting the response from the first cache allows the other cache value to be displayed in devtools properly.
Its behaving like devtools is using caches.match() internally instead of a cache.match() on the specific cache. And it looks like it is:
https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/cache_storage/inspector_cache_storage_agent.cc?l=657&rcl=f62d1dab8d952f2a63d30bb871e2f6e5996040c2
I think we just need to pass the cache_name in the query params there.
,
Jan 5
|
|||
►
Sign in to add a comment |
|||
Comment 1 by swarnasree.mukkala@chromium.org
, Dec 26