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<https://www.w3.org/TR/webcodecs-video-frame-metadata-registry/#dom-videoframemetadata>.
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<https://github.com/web-platform-tests/wpt/pull/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) Bug/Feature tracker https://issues.chromium.org/issues/414545889 ChromeStatus entry https://chromestatus.com/feature/5186046555586560 -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/PH7PR12MB8796A63AD68D836BD7E23130A6F2A%40PH7PR12MB8796.namprd12.prod.outlook.com.
