- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 May 2020 20:52:34 +0000
- To: public-webrtc-logs@w3.org
We've been working over the last year to [make the API robust](https://webrtchacks.com/min-duration-series-part-1-perfect-negotiation/). I recommend the [spec example](https://w3c.github.io/webrtc-pc/#perfect-negotiation-example). > why not fix the root cause? Because there's no guarantee that allowing JS to do things out of order on initial negotiation won't then happen again on renegotiation, as I mentioned https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-622085409. Most likely it would, and then it's much less clear how we'd resolve it correctly, as mentioned in https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-622272086. I'm happy to pick up the conversation there if you have ideas on how to solve it. I also suspect the "root cause" is or may have been a bug in Chrome. I'm going to rip out some wpt helpers to help find it, since being too lenient in tests appears to be coming back to bite us. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-623699246 using your GitHub account
Received on Monday, 4 May 2020 20:52:36 UTC