- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Aug 2018 20:53:07 +0000
- To: public-webrtc-logs@w3.org
It's possible that the way this is described in the spec already makes this a non-issue. The use of slots and updating those in tasks is certainly a better situation that for media elements in HTML. @alvestrand, perhaps this is at this point only a Chrome bug? Testing stuff like this is a bit tricky, it would requiring busy-waiting and looking for changes as well as checking frequently for an inconsistent state that should be impossible to observe, but such a test will still sometimes spuriously pass due to good (bad?) luck. -- GitHub Notification of comment by foolip Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1965#issuecomment-413681157 using your GitHub account
Received on Thursday, 16 August 2018 20:53:08 UTC