Re: RFC: WebApp timing

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

>