W3C home > Mailing lists > Public > public-web-perf@w3.org > July 2011

Re: Unified Timing: Navigation, Resource and User Timing Updates

From: Zhiheng Wang <zhihengw@google.com>
Date: Mon, 11 Jul 2011 11:40:32 -0700
Message-ID: <CAA1TnvXKBEJkVyq0YwACOXThHmSU5kxAcnucCjVFJX8jkhBesA@mail.gmail.com>
To: Jatinder Mann <jmann@microsoft.com>
Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
   Thanks for updating the drafts! Putting it down on the paper makes it
much clearer what
changes we are making.

   As Chris pointed out, this is a good time to check with browser vendors,
especially those with
NavigationTiming implemented, to validate the proposed changes at this
stage. I've been
debating but we could postpone some of the additional interfaces under
window.performance
to a following spec, when they are truly necessary.

  window.performance.getEntries();
  window.performance.getEntriesByType();
  window.performance.getEntriesByName();

cheers,
Zhiheng

On Fri, Jul 1, 2011 at 4:48 PM, Jatinder Mann <jmann@microsoft.com> wrote:

>  As per our discussion to unify all Web Performance Timing specifications
> with an inheritance model and consistent API for data retrieval, we have
> made updates to Navigation, Resource and User Timing specification. Please
> review these changes and provide feedback.****
>
> ** **
>
> Navigation Timing:
> http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
> ****
>
> ** **
>
> Resource Timing:
> http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourceTiming/Overview.html
> ****
>
> ** **
>
> User Timing:
> http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/UserTiming/Overview.html*
> ***
>
> ** **
>
> Have a great long weekend!****
>
> ** **
>
> Thanks,****
>
> Jatinder ****
>
> ** **
>
> ** **
>
Received on Monday, 11 July 2011 18:41:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:31 UTC