- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Nov 2019 17:52:22 +0000
- To: public-webrtc-logs@w3.org
@henbos @alvestrand It appears that the current Chrome behavior matches the specification. While there is some inconsistency between the behavior on the local and remote peer, this doesn't seem like a serious problem to me. The peer applying a remote offer will find that the objects become visible after calling createAnswer() and then setLocalDescription(Answer), so the delay in visibility is only due to execution time, not network delays. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2338#issuecomment-554002685 using your GitHub account
Received on Thursday, 14 November 2019 17:52:24 UTC