- From: Przemysław Pietrzkiewicz <ppi@google.com>
- Date: Wed, 2 Jul 2014 18:21:59 +0200
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: Arvind Jain <arvind@google.com>, public-web-perf <public-web-perf@w3.org>
Received on Wednesday, 2 July 2014 16:22:26 UTC
I recognize these are all important questions, but I don't see why these need answering in this case. Would you agree that it makes sense to record the navigationStart early (possibly adding new attributes for intermediate steps some consumers would not be interested in)? If yes, isn't moving the navigationStart for navigations in new browsing context to the time the context is created an improvement? Why does it require revisiting the definition for navigations in existing browsing contexts? Cheers, Przemek On Wed, Jul 2, 2014 at 6:15 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 7/2/14, 12:07 PM, Przemysław Pietrzkiewicz wrote: > >> Could you explain why? How is the time the user took to decide in the >> prompt related to performance? >> > > beforeunload events need not involve a prompt. > > Again, this comes back to what exactly we're trying to measure. If a > beforeunload event handler takes 5s to execute and there is no actual > unload prompts, should those 5s be included in the load time? > > What about if there is a prompt? Does it matter whether the 5s of > execution time came before or after the prompt? > > -Boris > >
Received on Wednesday, 2 July 2014 16:22:26 UTC