From 0382484c6a56476f26de1ebfd5944575e479aa2a Mon Sep 17 00:00:00 2001
From: Noam Rosenthal
+ Though `workerStart` is exposed in PerformanceResourceTiming, it
+ has a different meaning in Navigation Timing, as unlike subresources, a navigation may
+ trigger the activation or running of a service worker.
+ In the context of Navigation Timing, `workerStart` returns the timestamp measured
+ just before the worker has been activated or started. See [[service-workers]] for
+ a precise definition.
+
+ When a [=service worker=] is used as part of the navigation, The `fetchStart` overload
+ holds a different meaning than the meaning in
+
+
@@ -379,57 +399,82 @@ A {{PerformanceNavigationTiming}} has an associated null or [=service worker timing info=]
service worker timing.
-
The unloadEventStart getter steps are to return |this|'s
- [=previous document unload timing=]'s [=document unload timing info/unload event start time=].
-
- See unload event for more info. If the previous document and the current document have the same
+ origin, this timestamp is measured immediately
+ before the user agent starts the unload event
+ of the previous document. If there is no previous document or the
+ previous document has a different origin than the current document, this attribute will return
+ zero.
+
The unloadEventEnd getter steps are to return |this|'s
- [=previous document unload timing=]'s [=document unload timing info/unload event end time=].
- See unload event for more info. If the previous document and the current document have the same
+ origin, this timestamp is measured immediately
+ after the user agent handles the unload event
+ of the previous document. If there is no previous document or the
+ previous document has a different origin than the current document, this attribute will return
+ zero.
+
The domInteractive getter steps are to return
|this|'s [=document load timing=]'s [=document load timing info/DOM interactive time=]. See document readiness for more info.
+ This timestamp is measured before the user agent sets the
+ current document readiness to
+ "interactive".
The domContentLoadedEventStart getter steps are to return |this|'s
[=document load timing=]'s
[=document load timing info/DOM content loaded event start time=]. See DOMContentLoaded for more info.
+ This timestamp is measured before the user agent dispatches the
+ DOMContentLoaded
+ event.
The domContentLoadedEventEnd getter steps are to return
|this|'s [=document load timing=]'s
[=document load timing info/DOM content loaded event end time=]. See DOMContentLoaded
- event completes.
+ This timestamp is measured after the user agent completes handling of the
+ DOMContentLoaded
+ event.
The domComplete getter steps are to return
|this|'s [=document load timing=]'s [=document load timing info/DOM complete time=].
- See document readiness for more info.
+ This timestamp is measured before the user agent sets the
+ current document readiness to
+ "complete". See document readiness for a precise
+ definition.
The loadEventStart getter steps are to return
|this|'s [=document load timing=]'s [=document load timing info/load event start time=].
@@ -319,6 +328,17 @@
+
PerformanceResourceTiming
.
+ It returns the timestamp measured right before the {{FetchEvent}} is dispatched for
+ the [=service worker=]. The time difference between `workerStart` and `fetchStart` in
+ the document's navigation timing entry can be used to determine roughly how long it
+ took for the worker to be initialized or activated. See [[service-workers]] for
+ a precise definition.
+
This timestamp is measured before the user agent dispatches the + load event for the document. +
The loadEventEnd getter steps are to return |this|'s [=document load timing=]'s [=document load timing info/load event end time=].
+This timestamp is measured after the user agent completes handling the + load event for the document. +
The type getter steps are to run the |this|'s [=navigation type=].
@@ -538,6 +583,19 @@