Performance events triggered by cached script assets
Reported by
m...@bocoup.com,
Nov 28
|
|||
Issue description
Chrome Version : 70.0.3538.77
OS Version:
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari:
Firefox: OK
IE/Edge:
Script assets which are declared in the document `<head>` and cached by the
browser will trigger PerformanceResourceTiming events in a script that is
executed subsequently.
Steps to reproduce:
1. Disable the network cache in Chrome's Dev Tools
2. Visit http://w3c-test.org/resource-timing/single-entry-per-resource.html
3. Refresh the page multiple times, noting that the test passes consistently
4. Enable the network cache in Chrome's Dev Tools
5. Visit http://w3c-test.org/resource-timing/single-entry-per-resource.html
6. Refresh the page multiple times, noting that the test fails consistently
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/70.0.3538.77 Chrome/70.0.3538.77 Safari/537.36
,
Nov 28
Thanks for filing the issue.. Able to reproduce the issue on reported chrome version 70.0.3538.77 also on latest chrome 72.0.3623.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!
,
Nov 29
Since reporting this behavior, I've learned that it's not a bug at all (it's allowed by an intentionally-imprecise part of the Resource Timing specification). Discussion available here: https://github.com/web-platform-tests/wpt/pull/14270 Sorry for the noise!
,
Dec 4
|
|||
►
Sign in to add a comment |
|||
Comment 1 by vamshi.kommuri@chromium.org
, Nov 28