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

Re: RFC: WebApp timing

From: Michael Nordman <michaeln@google.com>
Date: Thu, 13 Aug 2009 00:49:26 -0700
Message-ID: <fa2eab050908130049m7af8cfc3k35368203b57e397f@mail.gmail.com>
To: Zhiheng Wang <zhihengw@google.com>
Cc: public-webapps@w3.org
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.

* 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'?

>
Received on Thursday, 13 August 2009 07:50:04 GMT

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