- From: Anderson Quach <Anderson.Quach@microsoft.com>
- Date: Tue, 15 Mar 2011 21:51:56 +0000
- To: public-web-perf <public-web-perf@w3.org>
Those failures are related to recent changes to testharness.js: http://lists.w3.org/Archives/Public/public-web-perf/2011Mar/0025.html We're waiting to hear back from James Graham. -----Original Message----- From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of Philippe Le Hegaret Sent: Tuesday, March 15, 2011 2:30 PM To: public-web-perf Subject: Implementation Report for Navigation Timing and test failure I created a preliminary implementation report as part of publishing the CR: http://www.w3.org/2011/03/navigation-timing-report.html (I'll let you guess which ones are Chrome 10 and IE9) Both implementations are failing http://w3c-test.org/webperf/tests/approved/test_document_open.htm 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 IE9 shows a 404 on blank_page_yellow.htm 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) Philippe
Received on Tuesday, 15 March 2011 21:52:31 UTC