- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Aug 2018 20:30:56 +0000
- To: public-webrtc-logs@w3.org
Chrome's bug can be triggered in WPT, it's just a matter of not waiting for the async operation (setLocal/RemoteDescription) to complete before reading the value of the current/pending local/remote descriptions. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1965#issuecomment-414452785 using your GitHub account
Received on Monday, 20 August 2018 20:30:57 UTC