- From: nztyrone36 via GitHub <sysbot+gh@w3.org>
- Date: Sat, 06 Feb 2021 17:18:43 +0000
- To: public-webrtc-logs@w3.org
On Sun, 7 Feb 2021 at 4:54 AM, Jan-Ivar Bruaroey <notifications@github.com> wrote: > To clarify, I think the intended behavior here is clear and discernible in > spite of these bugs: always queue a task to set state and fire relevant > change events immediately after, and queue a second task to open any data > channels. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webrtc-pc/issues/2622#issuecomment-774497903>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIR6PTWLSULD5HBMFA3UXETS5VQ3LANCNFSM4XGMMUMA> > . > What’s this all about -- GitHub Notification of comment by nztyrone36 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2622#issuecomment-774510134 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 6 February 2021 17:18:44 UTC