Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add non-normative notes for attributes. #159

Merged
merged 2 commits into from
Sep 27, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
83 changes: 64 additions & 19 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -312,13 +312,33 @@ <h3>
<li>If |workerTiming| is null, then return |this|'s prototype's `workerStart`.
<li>Return |workerTiming|'s [=service worker timing info/start time=].
</ol>
<p class="note">
Though `workerStart` is exposed in <a data-cite=
"RESOURCE-TIMING-2#dom-performanceresourcetiming">PerformanceResourceTiming</a>, 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.
</p>
</li>
<li>The `fetchStart` getter steps are to perform the following steps:
<ol>
<li>Let |workerTiming| be |this|'s [=PerformanceNavigationTiming/service worker timing=].
<li>If |workerTiming| is null, then return |this|'s prototype's `fetchStart`.
<li>Return |workerTiming|'s [=service worker timing info/fetch event dispatch time=].
</ol>
<p class="note">
When a [=service worker=] is used as part of the navigation, The `fetchStart` overload
holds a different meaning than the meaning in
<a data-cite="resource-timing-2#dom-performanceresourcetiming-requeststart">
<code>PerformanceResourceTiming</code></a>.
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.
</p>
</li>
</ul>
<p class="note">
Expand Down Expand Up @@ -379,57 +399,82 @@ <h3>

<p>A {{PerformanceNavigationTiming}} has an associated null or [=service worker timing info=]
<dfn data-dfn-for="PerformanceNavigationTiming">service worker timing</dfn>.

</p>

<p data-dfn-for='PerformanceNavigationTiming'>
The <dfn>unloadEventStart</dfn> getter steps are to return |this|'s
[=previous document unload timing=]'s [=document unload timing info/unload event start time=].
</li>
<p class="note">See <a data-cite=
"HTML/browsing-the-web.html#unloading-documents">unload event</a> for more info.</p>
</ol>
[=previous document unload timing=]'s [=document unload timing info/unload event start
time=].
<p class="note">If the previous document and the current document have the same
<a data-cite="html#concept-origin">origin</a>, this timestamp is measured immediately
before the user agent starts the <a data-cite=
"HTML/browsing-the-web.html#unloading-documents">unload</a> event
of the previous document. If there is no previous document or the
previous document has a different <a data-cite=
"html#concept-origin">origin</a> than the current document, this attribute will return
zero.
</p>
<p data-dfn-for='PerformanceNavigationTiming'>
The <dfn>unloadEventEnd</dfn> getter steps are to return |this|'s
[=previous document unload timing=]'s [=document unload timing info/unload event end time=].</li>
<p class="note">See <a data-cite=
"HTML/browsing-the-web.html#unloading-documents">unload event</a> for more info.</p>
</ol>
[=previous document unload timing=]'s
[=document unload timing info/unload event end time=].
<p class="note">If the previous document and the current document have the same
<a data-cite="html#concept-origin">origin</a>, this timestamp is measured immediately
after the user agent handles the <a data-cite=
"HTML/browsing-the-web.html#unloading-documents">unload</a> event
of the previous document. If there is no previous document or the
previous document has a different <a data-cite=
"html#concept-origin">origin</a> than the current document, this attribute will return
zero.
</p>
<p data-dfn-for='PerformanceNavigationTiming'>
The <dfn>domInteractive</dfn> getter steps are to return
|this|'s [=document load timing=]'s [=document load timing info/DOM interactive time=].</p>

<p class="note">See <a data-cite=
"HTML/dom.html#current-document-readiness">document readiness</a> for more info.
<p class="note">This timestamp is measured before the user agent sets the
<a data-cite="HTML/dom.html#current-document-readiness">current document readiness</a> to
<a data-cite="HTML/parsing.html#the-end">"interactive"</a>.
</p>
<p data-dfn-for='PerformanceNavigationTiming'>
The <dfn>domContentLoadedEventStart</dfn> getter steps are to return |this|'s
[=document load timing=]'s
[=document load timing info/DOM content loaded event start time=].</p>
<p class="note">See <a data-cite=
"HTML/parsing.html#the-end:event-domcontentloaded">DOMContentLoaded</a> for more info.
</p>
<p class="note">This timestamp is measured before the user agent dispatches the
<a data-cite="HTML/parsing.html#the-end:event-domcontentloaded">DOMContentLoaded</a>
event.
</p>
<p data-dfn-for='PerformanceNavigationTiming'>
The <dfn>domContentLoadedEventEnd</dfn> getter steps are to return
|this|'s [=document load timing=]'s
[=document load timing info/DOM content loaded event end time=].</p>
<p class="note">See <a data-cite=
"HTML/parsing.html#the-end:event-domcontentloaded">DOMContentLoaded
event</a> completes.
<p class="note">This timestamp is measured after the user agent completes handling of the
<a data-cite="HTML/parsing.html#the-end:event-domcontentloaded">DOMContentLoaded</a>
event.
</p>
<p data-dfn-for='PerformanceNavigationTiming'>
The <dfn>domComplete</dfn> getter steps are to return
|this|'s [=document load timing=]'s [=document load timing info/DOM complete time=].
<p class="note">See <a data-cite=
"HTML/dom.html#current-document-readiness">document readiness</a> for more info.
<p class="note">This timestamp is measured before the user agent sets the
<a data-cite="HTML/dom.html#current-document-readiness">current document readiness</a> to
<a data-cite="HTML/parsing.html#the-end">"complete"</a>. See <a data-cite=
"HTML/dom.html#current-document-readiness">document readiness</a> for a precise
definition.
</p>
<p data-dfn-for='PerformanceNavigationTiming'>
The <dfn>loadEventStart</dfn> getter steps are to return
|this|'s [=document load timing=]'s [=document load timing info/load event start time=].</p>
</p>
<p class="note">This timestamp is measured before the user agent dispatches the
<a data-cite="HTML/parsing.html#the-end:event-event-load">load</a> event for the document.
</p>
<p data-dfn-for='PerformanceNavigationTiming'>
The <dfn>loadEventEnd</dfn> getter steps are to return
|this|'s [=document load timing=]'s [=document load timing info/load event end time=].</p>
</p>
<p class="note">This timestamp is measured after the user agent completes handling the
<a data-cite="HTML/parsing.html#the-end:event-event-load">load</a> event for the document.
</p>
<p data-dfn-for='PerformanceNavigationTiming'>
The <dfn>type</dfn> getter steps are to run the |this|'s [=navigation type=].
</p>
Expand Down