Questions regarding AudioContext.playbackStats (formerly playoutStats) migration

[Hongchan Choi]

Hi Blink API Owners,

I am preparing to ship the Web Audio Playout Statistics API (Chrome Status: https://chromestatus.com/feature/5172818344148992). Following recent specification updates to align with standardized terminology, I am renaming the API surface and have a few process-related questions:

1. Chrome Status Title Update: Is it acceptable to simply rename the existing Chrome Status entry from "AudioContext.playoutStats" to "AudioContext.playbackStats"? The underlying functionality is unchanged, but the interface/prop name has shifted to match the spec.

2. To ensure zero breakage for the primary partner of the experimental implementation and to maintain UMA continuity, my current implementation exposes both the old and new API shapes simultaneously (only up to M146):

• AudioContext.playbackStats (New) and .playoutStats (Legacy alias).
• AudioPlaybackStats interface with [LegacyWindowAlias=AudioPlayoutStats].
• Properties like underrunDuration (New) and fallbackFramesDuration (Legacy alias via [ImplementedAs]).
• toJSON() output includes a superset of both new and legacy keys.

Do the API Owners have any concerns with shipping this "superset" approach for a transitional period (M146) to facilitate a non-breaking migration?

3. Intent to Ship UI: I am currently in the "Prepare to Ship" stage on Chrome Status, but I do not see the "Draft Intent to Ship email" generation button. Is there a specific prerequisite I might be missing, or should I proceed with a manual draft for blink-dev?

Thanks for your guidnace.

Best,

Hongchan

[Yoav Weiss (@Shopify)]

Hey Hongchan!

On Wed, Jan 14, 2026 at 9:55 PM 'Hongchan Choi' via blink-api-owners-discuss <blink-api-ow...@chromium.org> wrote:

Hi Blink API Owners,

I am preparing to ship the Web Audio Playout Statistics API (Chrome Status: https://chromestatus.com/feature/5172818344148992). Following recent specification updates to align with standardized terminology, I am renaming the API surface and have a few process-related questions:

1. Chrome Status Title Update: Is it acceptable to simply rename the existing Chrome Status entry from "AudioContext.playoutStats" to "AudioContext.playbackStats"? The underlying functionality is unchanged, but the interface/prop name has shifted to match the spec.

It seems fine to rename the chrome status entry.
 

2. To ensure zero breakage for the primary partner of the experimental implementation and to maintain UMA continuity, my current implementation exposes both the old and new API shapes simultaneously (only up to M146):

• AudioContext.playbackStats (New) and .playoutStats (Legacy alias).
• AudioPlaybackStats interface with [LegacyWindowAlias=AudioPlayoutStats].
• Properties like underrunDuration (New) and fallbackFramesDuration (Legacy alias via [ImplementedAs]).
• toJSON() output includes a superset of both new and legacy keys.

Can you only enable the legacy interface as part of the Origin Trial and keep the origin trial going for M146 to enable transition?
That's what folks typically do..
 

Do the API Owners have any concerns with shipping this "superset" approach for a transitional period (M146) to facilitate a non-breaking migration?

3. Intent to Ship UI: I am currently in the "Prepare to Ship" stage on Chrome Status, but I do not see the "Draft Intent to Ship email" generation button. Is there a specific prerequisite I might be missing, or should I proceed with a manual draft for blink-dev?

It's usually part of the "API owners" approval box

 

Thanks for your guidnace.

Best,

Hongchan

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAGJqXNur4wEik7aU2A9o%2B%2BaGShuAeM3BCsUUoWM3Z-mQ%2BJiUXA%40mail.gmail.com.

[Hongchan Choi]

Hi Yoav,

Thank you! That was very helpful.

Now the Intent to Ship is now out: https://groups.google.com/a/chromium.org/g/blink-dev/c/p-IHBp8Nw2Q

Best,

Hongchan