HTTP response status code in Resource Timing

[abinpaul1]

Request for position on an emerging web specification

• WebKittens who can provide input: @achristensen07

Information about the spec

• Spec Title: HTTP response status code in Resource Timing
• Spec URL: https://github.com/w3c/resource-timing/pull/335
• GitHub repository: https://github.com/w3c/resource-timing
• Issue Tracker: https://github.com/w3c/resource-timing/issues/90
• Explainer: https://github.com/abinpaul1/resource-timing/blob/explainer-resource-response-status/Explainers/Response_Status_Code.md

Design reviews and vendor positions

• TAG Design Review: https://github.com/w3ctag/design-reviews/issues/757
• Mozilla standards-positions issue: https://github.com/mozilla/standards-positions/issues/665

Bugs tracking this feature

• Chromium : https://bugs.chromium.org/p/chromium/issues/detail?id=1343293
• WebKit Bugzilla:
• Radar:

Anything else we need to know

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

[yoavweiss]

^^ @achristensen07

[abinpaul1]

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

[annevk]

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]

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]

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

[hober]

Closing as we've identified our position.