w3c / w3c/resource-timing

Expose a way to link a call to fetch to an individual PerformanceResourceTiming object

Open
#102 5 comments 19 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement requires Fetch integration
Dominant language
Bikeshed
Stars
135
Forks
40
PR merge metrics
No merged PRs in 30d

Description

(copy and pasting from https://github.com/whatwg/fetch/issues/491)

Problem

Currently the process of linking a fetch request to a specific resource timing object is imperfect. If there are two fetch api requests for the same resource that happen within a short time it's impossible to tell exactly which fetch call initiated which request, leading to some errors in performance logging. Orthogonally, if all a developer cares about is the perf result for a single fetch, having to use the whole performance api could be cumbersome.

Solution?

The ideal solution here (imo) is for there to be a way to get a resource timing object for a specific response. This could be accomplished by adding a method to response objects that give you a promise which will eventually resolve to the PerformanceResourceTiming object once it's ready.

Thoughs?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the copied context from WHATWG Fetch issue #491 and this issue's proposal; no implementation files or tests are named. Done would require an agreed specification change that links an individual fetch response to its PerformanceResourceTiming object, followed by identifying the affected Resource Timing spec sections and validation work.

Written by the indexing model from the issue text.

Assessment

Domain
api, performance, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.