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

HTTP response status code in Resource Timing #35

Closed
abinpaul1 opened this issue Jul 13, 2022 · 6 comments
Closed

HTTP response status code in Resource Timing #35

abinpaul1 opened this issue Jul 13, 2022 · 6 comments
Labels
from: Google Proposed, edited, or co-edited by Google. position: support topic: http Spec relates to the HTTP (Hypertext Transfer Protocol) family of protocols topic: performance venue: W3C Web Performance WG

Comments

@abinpaul1
Copy link

abinpaul1 commented Jul 13, 2022

Request for position on an emerging web specification

Information about the spec

Design reviews and vendor positions

Bugs tracking this feature

Anything else we need to know

Link to entry on the Chrome Platform Status: https://chromestatus.com/feature/5163838794629120

@yoavweiss
Copy link

@hober hober added topic: performance topic: http Spec relates to the HTTP (Hypertext Transfer Protocol) family of protocols venue: W3C Web Performance WG labels Sep 1, 2022
@othermaciej othermaciej added the from: Google Proposed, edited, or co-edited by Google. label Sep 25, 2022
@abinpaul1
Copy link
Author

abinpaul1 commented Oct 21, 2022

Hey @othermaciej,
I was curious about the from:Google label for this. This was added in response to developer interest for the feature. See w3c/resource-timing#90. I was wondering if the label was appropriate.

@annevk
Copy link
Contributor

annevk commented Oct 22, 2022

from: is supposed to reflect which entity is driving the work. I think Google is accurate here.

With response's status being guarded by CORS this seems reasonable to me, but would be good to hear from @achristensen07 in case there's any performance-specific feedback.

@achristensen07
Copy link

Perf overhead of this is basically zero. Since this exposes the exact same information as fetch status, I think we should just do it.

@marcoscaceres
Copy link
Contributor

Discussed with colleagues and we are supportive. Unless anyone objects, we will mark this as such in a week or so.

@hober
Copy link
Member

hober commented Mar 23, 2023

Closing as we've identified our position.

@hober hober closed this as completed Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
from: Google Proposed, edited, or co-edited by Google. position: support topic: http Spec relates to the HTTP (Hypertext Transfer Protocol) family of protocols topic: performance venue: W3C Web Performance WG
7 participants