- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Dec 2017 10:04:35 +0000
- To: public-webrtc-logs@w3.org
I think if you could design this again you'd have a single event potentially representing multiple operations. But the state things are in now it would make the most sense indeed to make each event represent the current state if possible (and seems like the reentrancy issues can be dealt with given @jan-ivar's comment). (Note that if you ever decide to have multiple "synchronous" events for a single state change you cannot really guard against it anymore for the subsequent events; XMLHttpRequest has this problem. DOM has the other problem though we're still somewhat hoping for mutation events to go away...) -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1691#issuecomment-353020410 using your GitHub account
Received on Wednesday, 20 December 2017 10:04:37 UTC