Skip to content

Commit d960038

Browse files
authored
docs: clarify requestStart behavior for canceled requests in Performance API (#41704)
Update documentation to clarify that canceled requests are still recorded by the Performance API, but may have requestStart value of 0, which can lead to calculation errors in performance metrics.
1 parent 986a94c commit d960038

File tree

1 file changed

+1
-0
lines changed
  • files/en-us/web/api/performanceresourcetiming/requeststart

1 file changed

+1
-0
lines changed

files/en-us/web/api/performanceresourcetiming/requeststart/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ The `requestStart` property can have the following values:
1919
- A {{domxref("DOMHighResTimeStamp")}} representing the time immediately before the browser starts requesting the resource from the server.
2020
- `0` if the resource was instantaneously retrieved from a cache.
2121
- `0` if the resource is a cross-origin request and no {{HTTPHeader("Timing-Allow-Origin")}} HTTP response header is used.
22+
- `0` if the resource is a canceled request.
2223

2324
When the {{domxref("PerformanceResourceTiming.firstInterimResponseStart", "firstInterimResponseStart")}} is non-zero, that indicates it should be the same value as `requestStart` for [supporting browsers](#browser_compatibility).
2425

0 commit comments

Comments
 (0)