Re: Implementation Report for Navigation Timing and test failure

On Tue, Mar 15, 2011 at 2:30 PM, Philippe Le Hegaret <plh@w3.org> wrote:

> Chrome10 reporting:
>  assert_equals:
>  loadEventEnd is the same after document open.
>  expected 1300224262997 got 1300224263067
>
>  assert_equals:
>  loadEventStart is the same after document open.
>  expected 1300224262997 got 1300224263067
>

This is fixed in Chrome 11.


> In addition, Chrome10 goes into an infinite loop for
>
> http://w3c-test.org/webperf/tests/approved/test_navigation_type_backforward.htm
> (it seems more of a problem with the test than a problem with the
> performance implementation)


This is due to a bug in the test harness tickling a bug in Chrome. The bug
in the test harness has been fixed in Mercurial, but hasn't been pushed to
w3c-test.org.

James