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 finalResponseHeadersStart to resource timing #1108

Open
noamr opened this issue Nov 6, 2024 · 2 comments
Open

Add finalResponseHeadersStart to resource timing #1108

noamr opened this issue Nov 6, 2024 · 2 comments

Comments

@noamr
Copy link

noamr commented Nov 6, 2024

Request for Mozilla Position on an Emerging Web Specification

  • Specification title: Add finalResponseHeadersStart to resource timing
  • Specification or proposal URL (if available): https://w3c.github.io/resource-timing/
  • Explainer URL (if available):
  • Proposal author(s) (@-mention GitHub accounts): @noamr @tunetheweb
  • Caniuse.com URL (optional):
  • Bugzilla URL (optional):
  • Mozillians who can provide input (optional): @sefeng211, Bas Schouten (not sure re the github handle?)
  • WebKit standards-position:

Other information

This was resolved in the WebPerfWG meeting, see minutes.

@tunetheweb
Copy link

Bas Schouten (not sure re the github handle?)

I think it's @Bas-moz

@sefeng211
Copy link
Member

finalResponseHeadersStart is the timing when the last response came. This is useful to see the timing differences for cases like early-hints where we have the first response which isn't the real response of the request.

We have no objection on this, it should be a positive for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Unscreened
Development

No branches or pull requests

3 participants