Thanks! Let's continue the review in that thread.
On 10/22/25 5:38 p.m., Anantanarayanan Iyengar wrote:
Hi Mike
I drafted the email using the Intent to ship template and posted it to
blink-dev and cc'ed you.
Thanks a bunch for your help and guidance.
Thanks
Ananta
------------------------------------------------------------------------
*From:* Mike Taylor <[email protected]>
*Sent:* Wednesday, October 22, 2025 2:02 PM
*To:* Anantanarayanan Iyengar <[email protected]>
*Cc:* [email protected] <[email protected]>; Sun Shin
<[email protected]>; [email protected] <[email protected]>
*Subject:* Re: [blink-dev] [Intent to Ship] WebCodecs
VideoFrame.metadata().rtpTimestamp (Chromium M146)
*External email: Use caution opening links or attachments*
On 10/22/25 4:08 p.m., Anantanarayanan Iyengar wrote:
Hi Mike
Thanks for the email.
I requested reviews for the Privacy, WP Security, Enterprise,
Debuggability, and Testing bits.
Thank you!
Could not find the Draft intent to ship button which generates the
email template. If you can share details
on where that is or why it doesn't show up for the feature (Maybe
some information in the prepare to ship or
earlier section is incomplete/incorrect?)
https://chromestatus.com/feature/5186046555586560?gate=5179324311011328
<https://chromestatus.com/feature/5186046555586560?gate=5179324311011328>
It can be a little hard to find - if you click on the "API Owners"
chip you should see a blue "Draft Intent to Ship email" on the
top-right (it's possible you didn't see this before because I had
marked this as "needs work", but it should be visible now).
Do we need to wait for the other reviews to finish before requesting
API Owners review?
Nope. API OWNER review can happen in parallel, but you should wait for
all review to be approved before shipping.
Thanks
Ananta
------------------------------------------------------------------------
*From:* Mike Taylor <[email protected]>
<mailto:[email protected]>
*Sent:* Wednesday, October 22, 2025 5:33 AM
*To:* Anantanarayanan Iyengar <[email protected]>
<mailto:[email protected]>
*Cc:* [email protected] <mailto:[email protected]>
<[email protected]> <mailto:[email protected]>; Sun Shin
<[email protected]> <mailto:[email protected]>;
[email protected] <mailto:[email protected]>
<[email protected]> <mailto:[email protected]>
*Subject:* Re: [blink-dev] [Intent to Ship] WebCodecs
VideoFrame.metadata().rtpTimestamp (Chromium M146)
You don't often get email from [email protected]
<mailto:[email protected]>. Learn why this is important
<https://aka.ms/LearnAboutSenderIdentification>
*External email: Use caution opening links or attachments*
Hey there,
This Intent to Ship is missing a lot of what API OWNERs need to
evaluate before approving. You should be able to generate a template
email from Chromestatus - feel free to reach out to me privately if
you can't figure that out.
Also, in your chromestatus entry, please request approvals for the
Privacy, WP Security, Enterprise, Debuggability, and Testing bits,
thanks.
thanks,
Mike
On 10/21/25 3:28 p.m., 'Anantanarayanan Iyengar' via blink-dev wrote:
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
<https://issues.chromium.org/issues/414545889>
ChromeStatus entry https://chromestatus.com/feature/5186046555586560
<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]
<mailto:[email protected]>.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/PH7PR12MB8796A63AD68D836BD7E23130A6F2A%40PH7PR12MB8796.namprd12.prod.outlook.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/PH7PR12MB8796A63AD68D836BD7E23130A6F2A%40PH7PR12MB8796.namprd12.prod.outlook.com?utm_medium=email&utm_source=footer>.
--
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/9c52e787-12fe-4b2d-a673-538559e91f55%40chromium.org.
