- From: henbos via GitHub <noreply@w3.org>
- Date: Wed, 22 Oct 2025 07:59:11 +0000
- To: public-webrtc-logs@w3.org
The fix we came up with in that CL was to roll back to a receptive state that aligns with the transceiver's currentDirection:
```
transceiver->internal()->set_receptive(
transceiver->internal()->current_direction() &&
RtpTransceiverDirectionHasRecv(
*transceiver->internal()->current_direction()));
```
This makes sense, and the fact that rollback isn't applicable in "pr-answer" means we can always trust currentDirection to be whatever state we should be in
--
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3081#issuecomment-3430924673 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 October 2025 07:59:12 UTC