W3C home > Mailing lists > Public > public-web-perf@w3.org > September 2010

[NavigationTiming] Lifetime of timing object

From: Anderson Quach <aquach@microsoft.com>
Date: Thu, 16 Sep 2010 01:23:30 +0000
To: "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <1E1FF4102DEA7A40AF9CC342044ECE5D2E191E31@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
We've been implicitly been taking the assumption that the lifetime of the NavigationTiming object should last the lifetime of the current navigation. It would be great if either in the processing model or in the definition of the interface be explicit of the lifetime of the timings.

Although some aspects of the lifetime of the window.performance.timing and window.performance.navigation is described about in steps 1 & 2, it may be useful to express about how long this information is retained. Either as a constraint statement after the processing model or in step 1. with the following text:

"The current window.performance.timing and window.performance.navigation instance is no longer valid after the unload of the current browsing context. Thus, the lifetime of the navigation and navigation info instance is tied to the lifetime of the current browsing context."

Anderson Quach
IE Program Manager
Received on Thursday, 16 September 2010 01:25:08 UTC

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