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

Re: Navigation Timing CR issues

From: Zhiheng Wang <zhihengw@google.com>
Date: Wed, 1 Jun 2011 10:51:01 -0700
Message-ID: <BANLkTimMfRYytMD0Ebo-gxw+=fz7BJkU_zcw1Ote5FMpP82vhw@mail.gmail.com>
To: Philippe Le Hegaret <plh@w3.org>
Cc: public-web-perf <public-web-perf@w3.org>, cam <cam@mcc.id.au>, Olli Pettay <Olli.Pettay@helsinki.fi>, Nic Jansma <Nic.Jansma@microsoft.com>, Boris Zbarsky <bzbarsky@mit.edu>, Christian Biesinger <cbiesinger@gmail.com>
    This is really helpful! I believe we've addressed most of the comments
in the current working draft, except the one below. Other may want to
confirm. And please let me know any other missing items.
* Navigation [Olli
 This is about how bfcache affects .navigation and .timing. We concluded
that these values should not changein case bfcache is used.     TODO: to fix
the test case at
 to deal with bfcache,      probably through adding and onunload handler.

On Wed, Jun 1, 2011 at 6:41 AM, Philippe Le Hegaret <plh@w3.org> wrote:

> While preparing the update for Navigation Timing, I made a list of
> issues we received since March 15:
>  http://www.w3.org/2011/06/navigation-timing-issues.html
> It would be helpful to know if we satisfied those comments (or not). I'm
> copying the individuals who submitted those comments as well, since it
> would also be useful to know if they were satisfied (or not).
> Check the latest editor's draft to see the most recent changes.
> Thank you,
> Philippe
> [1]
> http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
Received on Wednesday, 1 June 2011 17:51:26 UTC

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