Document AudioPlaybackStats

[chrisdavidmills]

Description

Chrome 146 adds support for AudioPlaybackStats, also known as the Playback statistics API for Web Audio: see https://chromestatus.com/feature/5172818344148992.

This PR adds documentation for the AudioPlaybackStats interface and the AudioContext.playbackStats property.

Motivation

Additional details

Related issues and pull requests

[github-actions]

Preview URLs (12 pages)

• /en-US/docs/Web/API/AudioContext/playbackStats
• /en-US/docs/Web/API/AudioContext
• /en-US/docs/Web/API/AudioPlaybackStats/averageLatency
• /en-US/docs/Web/API/AudioPlaybackStats/maximumLatency
• /en-US/docs/Web/API/AudioPlaybackStats/minimumLatency
• /en-US/docs/Web/API/AudioPlaybackStats/resetLatency
• /en-US/docs/Web/API/AudioPlaybackStats/toJSON
• /en-US/docs/Web/API/AudioPlaybackStats/totalDuration
• /en-US/docs/Web/API/AudioPlaybackStats/underrunDuration
• /en-US/docs/Web/API/AudioPlaybackStats/underrunEvents
• /en-US/docs/Web/API/AudioPlaybackStats
• /en-US/docs/Web/API/Web_Audio_API

(comment last updated: 2026-04-10 17:29:54)

[chrisdavidmills]

Technical reviewer: @hoch.

[hoch]

Some thoughts:

• The majority of the value from these properties are "a double-precision floating point value in seconds".
• I am not familiar to the convention of MDN, but the content I saw is mostly description of the API, not the actual meaning of implication of the feature or value. If this is the norm, then the current change looks fine.

LGTM; these are mostly nits anyway.

[chrisdavidmills]

Some thoughts:

Thanks for the review, @hoch.

* The majority of the value from these properties are "a double-precision floating point value in seconds".

I've added this detail to the detail pages for the relevant properties.

* I am not familiar to the convention of MDN, but the content I saw is mostly description of the API, not the actual meaning of implication of the feature or value. If this is the norm, then the current change looks fine.

I've tried to do a bit of this in the descriptions, especially in the interface landing page. What other kinds of details would you like to add? In general, on MDN, we try to get a balance of technical description and user-centric description.