Skip to content

fix(PerformanceResourceTiming): clarify startTime is not always fetchStart #45544

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.

Sign up for GitHub

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

Open
BaconMan1168 wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

fix(PerformanceResourceTiming): clarify startTime is not always fetchStart #45544

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion files/en-us/web/api/performanceresourcetiming/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ This interface extends the following {{domxref("PerformanceEntry")}} properties
- {{domxref("PerformanceEntry.name")}} {{ReadOnlyInline}}
- : Returns the resource's URL.
- {{domxref("PerformanceEntry.startTime")}} {{ReadOnlyInline}}
- : Returns the {{domxref("DOMHighResTimeStamp","timestamp")}} for the time a resource fetch started. This value is equivalent to {{domxref("PerformanceResourceTiming.fetchStart")}}.
- : Returns the {{domxref("DOMHighResTimeStamp","timestamp")}} for the time a resource fetch started. If there are no HTTP redirects, this value is equivalent to {{domxref("PerformanceResourceTiming.fetchStart")}}. If there are HTTP redirects, this value is the time the first fetch in the redirection started, whereas `fetchStart` returns the time immediately before the user agent starts to fetch the final resource in the redirection.

### Timestamps

Expand Down