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

Re: RFC: WebApp timing

From: Zhiheng Wang <zhihengw@google.com>
Date: Thu, 13 Aug 2009 03:00:41 -0700
Message-ID: <802863260908130300l5ec9374ej13dc900744e03b0a@mail.gmail.com>
To: Michael Nordman <michaeln@google.com>
Cc: public-webapps@w3.org
Hi, Michael,
   Good point indeed.

On Thu, Aug 13, 2009 at 12:49 AM, Michael Nordman <michaeln@google.com>wrote:

>
>> interface Window {
>
>
>>   readonly attribute Timing <http://www.corp.google.com/~zhihengw/no_crawl/html5/timing.html#timing-0> pageTiming;
>
>
>> };
>
> The pageTiming attribute represents the timing information related to the
>> current top-level browsing context. Each top-level browser context must have
>> a unique pageTiming attribute.
>
>
> You mention top-level browsing context specifically, not just browsing
> context.
>
> * Firstly, why not just 'browsing context'? Seems like these timings also
> apply to subframe navigations.
>

     Top level document is the main object we have been looking at. But as
you point out, the timing measures can also be applied to
subframes. (e.g., IE does have BeforeNavigate2 events for the root page and
each subframe.) And it's a good idea to accommodate
this case. I will see how I can make change accordingly.


>
> * Secondly, does that imply that accessing window.pageTiming from a nested
> frame returns the timing for its 'top' page? Or perhaps an 'empty' timing
> object or 'null'?
>

    I think we can use a new navigation type, say, navigate_frame. This
could be useful in some cases, e.g., for a search result page to determine
if it has been "framed" by a third party page.

thanks,
Zhiheng
Received on Thursday, 13 August 2009 10:01:19 GMT

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