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

[Navigation Timing] Clarification needed on DOM timers and document.open()

From: James Simonsen <simonjam@chromium.org>
Date: Thu, 30 Sep 2010 17:34:04 -0700
Message-ID: <AANLkTin=sXgN3ohB6T1MO+iC7HM4fW6O0sTuybqyd-Tx@mail.gmail.com>
To: public-web-perf@w3.org

The Navigation Timing spec says that the domLoading, domInteractive, and
domComplete timers should be set to the time immediately before the
document's readiness changes. What is the expected behavior when the
document reaches the same state multiple times?

For example, if document.open() is called, the document returns to the
loading state. Should the domLoading timer reflect the first time we reached
the loading state? Or the most recent?

The domContentLoaded timer has the same issue, since its associated event
can fire multiple times as well.

Received on Friday, 1 October 2010 20:27:18 UTC

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