- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 May 2019 22:22:34 +0000
- To: public-webrtc-logs@w3.org
It seems all browsers set the ratechange to 1 when setting a srcObject MediaStream. It seems Chrome, Firefox and Safari all keep/set it to 1 when setting srcObject to null. I would tend to keep these two behaviors. The fact that the setter does nothing in case of media stream has the small benefit of allowing an application to detect that setting a ratechange is a no-op. This should also preclude the second range change event. This is Chrome behavior and I think this is also the intended behavior of Safari. That would mean something like: 0.5, 1, 1, 1 As of the ratechange events, there should be one whenever changing the value, right? -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/599#issuecomment-497506935 using your GitHub account
Received on Thursday, 30 May 2019 22:22:36 UTC