Rename jitterBufferDelayhint to playoutDelayHint in RTCRtpReceiver. #19510
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wpt-pr-bot
approved these changes
Oct 4, 2019
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-1836508
branch
3 times, most recently
from
43b43a7
to
b154f6c
Compare
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-1836508
branch
6 times, most recently
from
069633b
to
d01fdba
Compare
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-1836508
branch
3 times, most recently
from
20b6cca
to
051e49a
Compare
Intent to ship here: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/4W4orKqA3Rs This concludes origin trial for RTCJitterBufferDelayHint described here: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Tgm4qiNepJc We embed it to RTCRtpReceiver under different name - playoutDelayHint. The spec describing it can be found here: https://henbos.github.io/webrtc-extensions/#dom-rtcrtpreceiver-playoutdelayhint Bug: webrtc:10287 Change-Id: I24edf1b6146a0ad1c8d979833e53a27617af44af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1836508 Commit-Queue: Ruslan Burakov <kuddai@google.com> Reviewed-by: Henrik Boström <hbos@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#708183}
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-1836508
branch
from
051e49a
to
11e1512
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Intent to ship here:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/4W4orKqA3Rs
This concludes origin trial for RTCJitterBufferDelayHint described here:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Tgm4qiNepJc
We embed it to RTCRtpReceiver under different name - playoutDelayHint. The
spec describing it can be found here:
https://henbos.github.io/webrtc-extensions/#dom-rtcrtpreceiver-playoutdelayhint
Bug: webrtc:10287
Change-Id: I24edf1b6146a0ad1c8d979833e53a27617af44af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1836508
Commit-Queue: Ruslan Burakov <kuddai@google.com>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708183}