[Intent to Ship] WebCodecs VideoFrame.metadata().rtpTimestamp (Chromium M146)

12 views
Skip to first unread message

Anantanarayanan Iyengar

unread,
3:33 PM (6 hours ago) 3:33 PM
to blin...@chromium.org, dalec...@chromium.org, Sun Shin
Hi Blink Dev/Owners

I’d like to signal intent to ship the new field rtpTimestamp on VideoFrame.metadata() as defined in the WebCodecs VideoFrame Metadata Registry.

What it adds:
The metadata().rtpTimestamp field allows applications using MediaStreamTrackProcessor for frame rendering to access the original RTP timestamp of a decoded video frame. 

Status:
• Chromium CLs and WPT tests have landed and merged.
• Tests are upstream in WPT PR 55392.
• Implementation behind --enable-blink-features=VideoFrameMetadataRtpTimestamp  flags has been running in Canary.
• We intend to flip the default-on flag for milestone M146.

Risk and monitoring:
• API change is additive — existing code continues to function without change.
• No known interoperability issues or security/privacy risks; full Self-Review has been carried out.
• Monitoring via WPT pass rate, usage counters, and developer feedback post-unlock.
Rollout plan:
• Flag flip to enabled-by-default in Chromium M146 (desktop and Android).
• No WebView / iOS surface at ship time; these inherit defaults later.
• No Finch experiment planned; will roll out to all users once approved.

Requests for Owners:
• Please review and approve the feature for the ship stage if it looks ok.
• Once approved, I will upload the flag flip CL and reference this intent.

Thanks
Ananta (Nvidia)




Reply all
Reply to author
Forward
0 new messages