W3C home > Mailing lists > Public > public-web-perf@w3.org > January 2012

Re: [minutes] 2012-01-25 Web Performance WG Teleconference #59

From: James Simonsen <simonjam@chromium.org>
Date: Tue, 31 Jan 2012 12:28:48 -0800
Message-ID: <CAPVJQik0DAB=hFvXuhacWTNJznhG73OrWRxJQ_GG6o1-DqD-yQ@mail.gmail.com>
To: "public-web-perf@w3.org" <public-web-perf@w3.org>
On Wed, Jan 25, 2012 at 2:39 PM, Karen Anderson (IE) <
Karen.Anderson@microsoft.com> wrote:

>  The test test_timing_attributes_order.htm regarding using sleeps in the
> unload handlers of the previous document are disallowed for Chrome as James
> pointed out on the mailing list.  It looks like the decision in today’s
> call was to just to verify the order and not the time of the unload
> events.  However, there was a past thread (attached) on the desire to have
> a test to ensure that the time between unloadEventStart/End only captured
> the onunload and not the onbeforeunload event.  What changed our minds?

Thanks for the thread. I didn't remember why we wanted this.

Maybe there's another way we can test this. If we record the timestamps
during beforeunload and unload, we should be able to compare that against
the navigationStart value. We'll have to use an <iframe> so that we have
the same monotonic clock. And to make sure we only use monotonic time on
all platforms, we may need to wait until we have window.performance.now().

Received on Tuesday, 31 January 2012 20:29:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:32 UTC