- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Apr 2017 15:30:23 +0000
- To: public-webrtc-logs@w3.org
Note that this kind of explanation exists currently for `RTCDataChannel.bufferedAmount`: > The bufferedAmount attribute must return the number of bytes of application data (UTF-8 text and binary data) that have been queued using send() but that, as of the last time the event loop started executing a task, had not yet been transmitted to the network. (This thus includes any text sent during the execution of the current task, regardless of whether the user agent is able to transmit text asynchronously with script execution.) Meaning that within an individual task execution, the value of `bufferedAmount` doesn't change, unless `send()` is called, causing it to increase. Here's one idea for what to say: "Unless otherwise stated, all `readonly` attributes must behave as though they return the value of an internal slot, which is only updated inside a queued microtask." -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1111#issuecomment-292211247 using your GitHub account
Received on Thursday, 6 April 2017 15:30:33 UTC