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

Use response body info instead of timing info for body sizes #321

Merged
merged 5 commits into from
Jun 17, 2022

Conversation

noamr
Copy link
Contributor

@noamr noamr commented Mar 20, 2022

As part of whatwg/fetch#1413

Those numbers are per-response and not per-fetch, so they need to be
treated separately.


Preview | Diff

Copy link
Contributor

@yoavweiss yoavweiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@yoavweiss yoavweiss added this to Triage in Triage May 5, 2022
@yoavweiss
Copy link
Contributor

@noamr - Can you take a look to see why the bots are unhappy?

@yoavweiss yoavweiss moved this from Triage to Just Work™ in Triage May 5, 2022
@noamr
Copy link
Contributor Author

noamr commented May 5, 2022

@noamr - Can you take a look to see why the bots are unhappy?

The fetch PR needs to be merged first

noamr added 2 commits May 26, 2022 13:53
Those numbers are per-response and not per-fetch, so they need to be
treated separately.
@noamr noamr changed the title Use resource info instead of timing info for body sizes Use response body info instead of timing info for body sizes May 26, 2022
annevk pushed a commit to whatwg/fetch that referenced this pull request Jun 17, 2022
As long as fetch callers pass in the necessary data through the request concept, they will not have to make additional calls to get timing reported accurately. Note that this does not work if callers want to use useParallelQueue.

Downstream PRs:
* whatwg/html#7722
* whatwg/xhr#347
* w3c/csswg-drafts#7355
* w3c/beacon#75
* w3c/resource-timing#321
* https://github.com/w3c/navigation-timing/pull/1760

Closes #1208 and closes w3c/navigation-timing#131.
@noamr noamr closed this Jun 17, 2022
@noamr noamr reopened this Jun 17, 2022
@yoavweiss
Copy link
Contributor

Still LGTM

@noamr
Copy link
Contributor Author

noamr commented Jun 17, 2022

Still LGTM

Thanks, waiting for XREF to be updated before merging

@noamr noamr merged commit d1f319e into gh-pages Jun 17, 2022
@noamr noamr deleted the resource-info branch June 17, 2022 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Triage
Just Work™
Development

Successfully merging this pull request may close these issues.

None yet

2 participants