- From: Tony Gentilcore <tonyg@google.com>
- Date: Wed, 18 Jan 2012 17:10:19 +0000
- To: Philippe Le Hegaret <plh@w3.org>
- Cc: Jatinder Mann <jmann@microsoft.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
On Wed, Jan 18, 2012 at 4:54 PM, Philippe Le Hegaret <plh@w3.org> wrote: > On Wed, 2012-01-18 at 11:40 -0500, Philippe Le Hegaret wrote: >> > On Wed, Jan 18, 2012 at 5:03 AM, Jatinder Mann <jmann@microsoft.com> wrote: >> > > Discuss Navigation Timing to PR >> >> Btw, we published a new draft of Navigation Timing yesterday. So, unless >> someone finds a mistake, no change will be applied for the PR version: >> http://www.w3.org/TR/2012/CR-navigation-timing-20120117/ > > Rerunning the tests one more time, I notice some failures on Chrome: > http://w3c-test.org/webperf/tests/approved/navigation-timing/html5/test_navigation_type_reload.html > http://w3c-test.org/webperf/tests/approved/navigation-timing/html5/test_timing_attributes_order.html > > but the results are inconsistent: > > http://w3c-test.org/framework/details/nav-timing-default/test_navigation_type_reload/ > http://w3c-test.org/framework/details/nav-timing-default/test_timing_attributes_order/ > > So, it seems more a glitch than anything that we should worry about. Can > someone confirm that? The test_timing_attributes_order.html failure about the unload handler is the new test that we talked about last week. It is my AI to verify that Chrome approves the test update. Not sure about the other test, did something change there recently as well? > > Philippe >
Received on Wednesday, 18 January 2012 17:11:27 UTC