- From: James Simonsen <simonjam@chromium.org>
- Date: Wed, 2 Mar 2011 17:40:22 -0800
- To: public-web-perf <public-web-perf@w3.org>
Received on Thursday, 3 March 2011 01:40:55 UTC
On Wed, Mar 2, 2011 at 12:16 PM, Anderson Quach <aquach@microsoft.com>wrote: > * > Navigation timing* > > *AndersonQuach:* No additional tests for this week, Microsoft is in the > process of being updated. > ... If there is no work around are we okay with a manual back_forward? > > *TonyG:* If there is no workaround I'm okay with a manual test. > This turned out to be a bug in testharness.js, which then tickled a bug in WebKit. The harness is inadvertently changing window.name as the test executes. When that's fixed, the automated back_forward test runs fine. We're okay with approving test_navigation_type_backforward.htm as is now. James
Received on Thursday, 3 March 2011 01:40:55 UTC