Skip to content

Include end time & render-blocking in opaque responses - #1953

Merged
annevk merged 4 commits into
mainfrom
response-end
Aug 25, 2026
Merged

Include end time & render-blocking in opaque responses#1953
annevk merged 4 commits into
mainfrom
response-end

Conversation

@noamr

@noamr noamr commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Resource timing always includes responseEnd and renderBlocking, even when TAO is omitted.

Closes #1945

(See WHATWG Working Mode: Changes for more details.)


Preview | Diff

noamr added 3 commits August 24, 2026 11:19
Resource timing always includes `responseEnd`, even when TAO is omitted.

Closes #1945
@noamr noamr changed the title Include end time in opaque responses Include end time & render-blocking in opaque responses Aug 24, 2026
Comment thread fetch.bs Outdated
@annevk
annevk merged commit f1aff91 into main Aug 25, 2026
2 checks passed
@annevk
annevk deleted the response-end branch August 25, 2026 06:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Creating opaque timing info discards the end time, causing responseEnd to be zero after a failed TAO check

2 participants