- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Tue, 24 Apr 2012 23:42:02 -0400
- To: "Karen Anderson (IE)" <Karen.Anderson@microsoft.com>
- CC: "public-web-perf@w3.org" <public-web-perf@w3.org>
On 4/24/12 11:37 PM, Karen Anderson (IE) wrote:
> Hi Boris,
>
> The http://w3c-test.org/webperf/tests/approved/navigation-timing/html5/test_timing_attributes_order.html test is failing the window.performance.timing.loadEventEnd> 0 and window.performance.timing.loadEventEnd> loadEventStart with this call: test_timing_order('loadEventEnd', 'loadEventStart');
Yes, this is because it's assuming things that it shouldn't be assuming;
in particular it assumes that the firing of the onload event of <iframe>
happens async after the firing of the onload event of the window inside
the iframe, which is not required by this spec. As in, the test is
broken. I've raised that on this list in the past.
For what it's worth, fixing the test should be pretty easy: just don't
read loadEventEnd synchronously from onload; do it off a timeout instead.
I'm sorry if I didn't make that clear in
http://lists.w3.org/Archives/Public/public-web-perf/2012Apr/0028.html
-Boris
Received on Wednesday, 25 April 2012 03:42:32 UTC