w3c / w3c/resource-timing

Resource Timing Buffer/Secondary Buffer properties have vague location

Open
#414 0 comments 0 reactions 1 assignee View on GitHub

@yoavweiss is already working on this.

Since May 9, 2025.

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

Description

https://w3c.github.io/resource-timing/#sec-extensions-performance-interface says "Each ECMAScript global environment has ..." followed by a bunch of buffer and integer properties.

  • A resource timing buffer size limit which should initially be 250 or greater.
  • A resource timing buffer current size which is initially 0.
  • A resource timing buffer full event pending flag which is initially false.
  • A resource timing secondary buffer current size which is initially 0.
  • A resource timing secondary buffer to store PerformanceResourceTiming objects that is initially empty.

The statement "ECMAScript global environment" links to https://webidl.spec.whatwg.org/#es-environment, which is not nearly specific enough for an implementation to decide where to place the properties.

I would expect them to be defined as existing on one of:

  • Every WindowOrWorkerGlobalScope instance
  • Every HTML Environment Settings Object
  • Certain categories of ESOs
  • Each Agent
  • Each Agent Cluster
  • One instance for the User Agent itself (still vague, but better vague)

What entity is supposed to own these buffers? cc @noamr

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.