Wotcher TAG!

I'm requesting a TAG review of HTTP Status Code in Resource Timing.

Adds a field responseStatusCode to PerfomanceResourceTiming which holds an integer corresponding to HTTP status code returned when fetching the resource.

• Explainer: https://github.com/abinpaul1/resource-timing/blob/explainer-resource-response-status/Explainers/Response_Status_Code.md
• Specification URL: https://github.com/w3c/resource-timing/pull/335
• Tests: https://github.com/web-platform-tests/wpt/pull/34828
• User research: None
• Security and Privacy self-review: https://github.com/abinpaul1/resource-timing/blob/explainer-resource-response-status/Explainers/Response_Status_Code.md#self-review-questionnaire-security-and-privacy
• Primary contacts (and their relationship to the specification):
  • Abin K Paul (@abinpaul1), spec author
  • Yoav Weiss (@yoavweiss), Google, spec mentor
• Organization(s)/project(s) driving the specification: Google
• Key pieces of existing multi-stakeholder review or discussion of this specification:
  • Discussion thread: https://github.com/w3c/resource-timing/issues/90
• External status/issue trackers for this specification: https://chromestatus.com/feature/5163838794629120

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines: September 1, 2022
• The group where the work on this specification is currently being done: W3C Web Performance WG
• Major unresolved issues with or opposition to this specification: None
• This work is being funded by: Google

You should also know that...

We'd prefer the TAG provide feedback as :

💬 leave review feedback as a comment in this issue and @-notify @abinpaul1 @yoavweiss