- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Dec 2019 02:46:25 +0000
- To: public-webrtc-logs@w3.org
@Pehrsons Firefox implementation of `CnavasCaptureMediaStreamTrack` has `onmute`, `onunmute`, and `onended` properties. Have tested various code in order to determine under what circumstances any of those events are fired at Firefox. The events are not fired under any circumstances that have tried testing at Firefox 70 or Nightly 73. If from your interpretation of the specification Firefox implementation is compliant with the same, then `onmute`, `onunmute`, and `onended` will never be fired in any version of Firefox. Therefore those properties should be removed from Firefox implementation. Chromium does fire attached `onmute` and `onunmute` events. If Chromium is not in compliance with the specification then the specification should remove make it clear that `CanvasCaptureMediaStreamTrack` does not fire `onmute`, `onunmute`, `ended` events, so that those properties can be removed from all implementations accordingly. Am able to utilize either implementation. At Chromium `mute` event fired can be used aa a mechanism to signal an image needs to be drawn onto the canvas to keep the `MediaStream` data flowing. At Firefox, since `CanvasCaptureMediaStreamTrack` does not fire `mute` under any circumstances the `MediaStream` has no chance of ever becoming muted or inactive. Of course, this leaves the fact that interoperability for `CanvasCaptureMediaStreamTrack` between Chromium and Firefox implementations is null and void, for whatever that fact is worth. -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-fromelement/issues/82#issuecomment-562409142 using your GitHub account
Received on Friday, 6 December 2019 02:46:27 UTC