- From: 陈智昌 <willchan@chromium.org>
- Date: Fri, 12 Apr 2013 15:54:54 -0700
- To: James Simonsen <simonjam@google.com>
- Cc: public-web-perf <public-web-perf@w3.org>
Received on Friday, 12 April 2013 22:55:21 UTC
I think "network layer cache" should be redefined in such a way to make Blink's behavior incompliant. The Blink memory cache is just another cache in the cache hierarchy. On Fri, Apr 12, 2013 at 3:40 PM, James Simonsen <simonjam@google.com> wrote: > The Resource Timing spec says: > > "Resources that are retrieved from the user agent's networking layer cache > must be included as PerformanceResourceTiming objects in the Performance > Timeline." > > What exactly constitutes a "networking layer cache?" Blink's memory cache > seems to behave differently than IE10's. When navigating pages on the same > site, Blink uses the "in-memory cache" and reuses subresources without > fetching. That means we don't report Resource Timing for these resources. > IE10 seems to always report resources in the same circumstances. > > To try it out, visit webpagetest.org. Note the "site.js loaded in x > milliseconds" at the bottom of the page. Browse to the "About" page on > webpagetest.org. That message disappears on Chrome, it shows a new value > on IE10. > > Are we both compliant in our own ways? Or do we need to better define > "network layer cache?" > > James >
Received on Friday, 12 April 2013 22:55:21 UTC