W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

R

From: Z <zhihengw@google.com>
Date: Thu, 17 Sep 2009 00:36:51 -0700
Message-ID: <802863260909170036t7ad55599xeefe5f5901a88518@mail.gmail.com>
To: p
   Somehow this message got lost so I am sending it again.

On Mon, Sep 14, 2009 at 4:01 PM, Zhiheng Wang <zhihengw@google.com> wrote:

>    Added some minor updates to incorporate the feedbacks. (Sorry for the
> long pause. I've been in absence for the past couple weeks.)
>   1) the window.pageTiming attribute should be available for each browsing
> context, not only the top-level one.
>   2) timing values are now in double/float so granularities finer than msec
> are possible, even though not mandated yet.
>
> cheers,
> Z
>
>
> On Wed, Aug 12, 2009 at 6:12 PM, Zhiheng Wang <zhihengw@google.com> wrote:
>
>> Hello,
>>
>>    We recently started a draft to provide timing-related APIs in browsers.
>> The goal is to add the missing pieces in webapp latency measurements
>> using Javascript. As a starter, right now we've only include a
>> minimum set of interfaces we consider necessary, which mainly focuse on
>> the time and type of the
>> navigation.
>>
>>    The first cut of the draft is attached below. It's sketchy but should
>> hold much of our ideas. We are
>> still actively working on it. Any interest and feedback on the draft are
>> highly welcome.
>>
>> cheers,
>> Zhiheng
>>
>
>


Received on Thursday, 17 September 2009 07:37:39 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:33 GMT