- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 19 Oct 2011 14:12:57 -0400
- To: "Karen Anderson (IE)" <Karen.Anderson@microsoft.com>
- CC: Philippe Le Hegaret <plh@w3.org>, "public-web-perf@w3.org" <public-web-perf@w3.org>
On 10/19/11 2:05 PM, Karen Anderson (IE) wrote: > What I find interesting is that IE and Chrome always have loadEventStart == loadEventEnd in both the onload event and in the callback. Which exact load event are you observing in this case? That's not clear from the script. I suspect that in IE and Chrome it matters > In FF, after yielding via setTimeout(0), loadEventStart == loadEventEnd == loadEventStart within the onload event handler. At that point you're no longer inside the onload event handler. > Seems that if there is no delta between the end of the onload handler and the start of the setTimeout callback What makes you think there isn't? The testcase doesn't measure this. > then the loadEventEnd could be set during the onload event handler. loadEventEnd is the time when the load event dispatch is complete and all load listeners have been run. How can it possibly be set before dispatch of the load event is complete? This is why the spec explicitly says that loadEventEnd returns 0 before dispatch of the load event completes. > Given that, I think the test is correct. What are your thoughts? My main thought at the moment is that you misunderstood the problem with the test... -Boris
Received on Wednesday, 19 October 2011 18:13:27 UTC