Skip to content

Commit

Permalink
chore: tidy up index.html (#294)
Browse files Browse the repository at this point in the history 
Co-authored-by: noamr <noamr@users.noreply.github.com>
  • Loading branch information
@github-actions @noamr
github-actions[bot] and noamr committed Sep 29, 2021
1 parent f9b2bb6 commit 35a3ec0
Showing 1 changed file with 56 additions and 40 deletions.
96 changes: 56 additions & 40 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -290,18 +290,22 @@ <h3>
This section is non-normative.
</p>
<p>
Resource [=Request=]s [=fetch=]ed by a non-null [=request/client=] are included as
<a>PerformanceResourceTiming</a> objects in the [=request/client=]'s
[=environment settings object/global object=]'s <a data-cite=
"PERFORMANCE-TIMELINE-2#performance-timeline">Performance Timeline</a>, unless excluded
from the timeline as part of the [=fetch|fetching process=]. Resources that are retrieved
from <a data-cite="HTML#relevant-application-cache">relevant application caches</a> or
local resources are included as <a>PerformanceResourceTiming</a> objects in the
<a data-cite="PERFORMANCE-TIMELINE-2#performance-timeline">Performance Timeline</a>.
Resources for which the [=fetch=] was initiated, but was later aborted (e.g. due to a
network error) are included as <a>PerformanceResourceTiming</a> objects in the
<a data-cite="PERFORMANCE-TIMELINE-2#performance-timeline">Performance Timeline</a>, with
their start and end timing.
Resource [=Request=]s [=fetch=]ed by a non-null [=request/client=]
are included as <a>PerformanceResourceTiming</a> objects in the
[=request/client=]'s [=environment settings object/global object=]'s
<a data-cite=
"PERFORMANCE-TIMELINE-2#performance-timeline">Performance
Timeline</a>, unless excluded from the timeline as part of the
[=fetch|fetching process=]. Resources that are retrieved from
<a data-cite="HTML#relevant-application-cache">relevant application
caches</a> or local resources are included as
<a>PerformanceResourceTiming</a> objects in the <a data-cite=
"PERFORMANCE-TIMELINE-2#performance-timeline">Performance
Timeline</a>. Resources for which the [=fetch=] was initiated, but
was later aborted (e.g. due to a network error) are included as
<a>PerformanceResourceTiming</a> objects in the <a data-cite=
"PERFORMANCE-TIMELINE-2#performance-timeline">Performance
Timeline</a>, with their start and end timing.
</p>
<p>
Examples:
Expand Down Expand Up @@ -473,10 +477,10 @@ <h3>
info/start time=] and <a>this</a>'s <a>relevant global
object</a>.
</p>

<p class='note'>
`startTime` is measured right at the start of the [=fetch=], before any redirects.
See <a data-cite="FETCH#fetching">fetching</a>.
`startTime` is measured right at the start of the [=fetch=],
before any redirects. See <a data-cite=
"FETCH#fetching">fetching</a>.
</p>
</dd>
<dt>
Expand All @@ -500,32 +504,44 @@ <h3>
<dfn>initiatorType</dfn> getter steps are to return the <a data-for=
"PerformanceResourceTiming">initiator type</a> for <a>this</a>.
</p>
<p class='note'>`initiatorType` returns one of the following values:
<ul class='note'>
<li>The same value as the {{Element/localName}} of an [=element=], if the request is a
result of processing an HTML element;</li>

<li><dfn>"css"</dfn>, if the request is a result of processing a CSS
<p class='note'>
`initiatorType` returns one of the following values:
</p>
<ul class='note'>
<li>The same value as the {{Element/localName}} of an [=element=], if
the request is a result of processing an HTML element;
</li>
<li>
<dfn>"css"</dfn>, if the request is a result of processing a CSS
<a data-xref-type="css-function">url()</a> directive such as
<code>@import url()</code> or <code>background: url()</code>; [[CSS-VALUES]]</li>

<li><dfn>"navigation"</dfn>, if the request is a [=navigation request=];</li>

<li><dfn>"xmlhttprequest"</dfn>, if the request is a result of processing an
{{XMLHttpRequest}};</li>

<li><dfn>"fetch"</dfn>, if the request is the result of processing the
{{WindowOrWorkerGlobalScope/fetch()}} method;</li>

<li><dfn>"beacon"</dfn>, if the request is the result of processing the
{{Navigator/sendBeacon()}} method; [[BEACON]]</li>

<li><dfn>"other"</dfn>, if none of the above conditions match.</li>
</ul>
<p class='note'>The setting of `initiatorType` is done at the different places where a resource timing
entry is reported, such as the [=fetch=] standard.

<p data-dfn-for="PerformanceResourceTiming">
<code>@import url()</code> or <code>background: url()</code>;
[[CSS-VALUES]]
</li>
<li>
<dfn>"navigation"</dfn>, if the request is a [=navigation
request=];
</li>
<li>
<dfn>"xmlhttprequest"</dfn>, if the request is a result of
processing an {{XMLHttpRequest}};
</li>
<li>
<dfn>"fetch"</dfn>, if the request is the result of processing the
{{WindowOrWorkerGlobalScope/fetch()}} method;
</li>
<li>
<dfn>"beacon"</dfn>, if the request is the result of processing the
{{Navigator/sendBeacon()}} method; [[BEACON]]
</li>
<li>
<dfn>"other"</dfn>, if none of the above conditions match.
</li>
</ul>
<p class='note'>
The setting of `initiatorType` is done at the different places where
a resource timing entry is reported, such as the [=fetch=] standard.
</p>
<p data-dfn-for="PerformanceResourceTiming">
The <dfn>workerStart</dfn> getter steps are to <a>convert fetch
timestamp</a> for <a>this</a>'s <a data-for=
"PerformanceResourceTiming">timing info</a>'s [=fetch timing
Expand Down

0 comments on commit 35a3ec0

Please sign in to comment.