- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Apr 2019 09:58:42 +0000
- To: public-webrtc-logs@w3.org
Chrome's implementation, likely the cause of all of this confusion, has been fixed. Reading the spec again it seems pretty straight forward: "When the bufferedAmount decreases from above this threshold to equal or below it, the bufferedamountlow event fires." I'm closing this issue. Feel free to object, but if so let me know what you think the example should contain. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1979#issuecomment-486608271 using your GitHub account
Received on Thursday, 25 April 2019 09:58:43 UTC