Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 4 users
Status: Assigned
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Task

Sign in to add a comment
WebRTC Frame Logging API
Project Member Reported by, May 23 Back to list
Change description:
Implement WebRTC Frame Logging API,

Changes to API surface:
Implement new API:

Public standards discussion:

Support in other browsers:
Internet Explorer: No
Firefox: No
Safari: No

Components: Blink>WebRTC>Video
Great, I am currently implementing an internal part of this API: calculating and propagating timestamps. How it would be reported to user application is not really decided. For now we will live with a work around. I doubt that this API will be implemented with quarter. Eventually we should transition to using this API.
 Issue 695223  has been merged into this issue.
Is it possible to add to specification 3 more timestamps? The capture time and two timestamps for possible in-network RTP processor. The latter two will have application-specific meaning.
Labels: migrated-launch-owp Type-Task
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here:

For any questions, please contact owencm, sshruthi, larforge
Sign in to add a comment