Skip to content

Clarify that synchronous rejection happens for audio receivers #247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 24, 2025
Merged

Clarify that synchronous rejection happens for audio receivers #247

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
36c23fb
Clarify that synchronous rejection happens for audio receivers
youennf Apr 24, 2025
ae9fdcb
Update index.bs
youennf Apr 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1070,7 +1070,7 @@ If the promise is associated to several rid values, it will be resolved when the

The <dfn abstract-op>send request key frame algorithm</dfn>, given |promise| and |depacketizer|, is defined by running these steps:
1. If |depacketizer| is undefined, reject |promise| with {{InvalidStateError}}, abort these steps.
1. If |depacketizer| is not processing video packets, reject |promise| with {{InvalidStateError}}, abort these steps.
1. If |depacketizer| belongs to an audio {{RTCRtpReceiver}}, reject |promise| with {{InvalidStateError}}, abort these steps.
1. [=In parallel=], run the following steps:
1. If sending a Full Intra Request (FIR) by |depacketizer|'s receiver is not deemed appropriate, [=resolve=] |promise| with undefined and abort these steps.
Section 4.3.1 of [[RFC5104]] provides guidelines of how and when it is appropriate to sending a Full Intra Request.
Expand Down