- From: Tony Gentilcore <tonyg@google.com>
- Date: Tue, 1 Feb 2011 14:49:17 -0800
- To: Anderson Quach <aquach@microsoft.com>
- Cc: public-web-perf <public-web-perf@w3.org>
We have two tests for consideration: 1. http://w3c-test.org/webperf/tests/submission/Google/NavigationTiming/test_document_open.htm Waits until all times are available and caches them. Then does a document.write() to blow away the entire document. Tests that timings were not changed. 2. http://w3c-test.org/webperf/tests/submission/Google/NavigationTiming/test_navigate_within_document.htm Waits until all times are available and caches them. Then appends a URL fragment (#1) to location.href. Tests that timings were not changed. On Mon, Jan 31, 2011 at 9:11 PM, Tony Gentilcore <tonyg@google.com> wrote: > Cool, thanks for the new tests. > >> test_performance_attributes_exist.htm > LGTM > >> test_readwrite.htm > LGTM > >> test_timing_client_redirect.htm > The third test which tests that the navigation type is TYPE_NAVIGATE > isn't correct. If I reload the page, it fails because the navigation > type is correctly TYPE_RELOAD. The three navigation types each need > tests which navigate an iframe using location.href='page2.html' for > TYPE_NAVIGATE, location.reload() for TYPE_RELOAD and history.back() > for TYPE_BACK_FORWARD. We can't rely on any test of navigation type in > the main frame. > >> test_unique_performance_objects.htm > LGTM >
Received on Tuesday, 1 February 2011 22:50:21 UTC