W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2018

[mediacapture-record] Not clear if onpause/onresume should not be fired if it is already paused/recording.

From: Bumsik Kim via GitHub <sysbot+gh@w3.org>
Date: Mon, 08 Oct 2018 23:02:50 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-367982173-1539039769-sysbot+gh@w3.org>
kbumsik has just created a new issue for https://github.com/w3c/mediacapture-record:

== Not clear if onpause/onresume should not be fired if it is already paused/recording. ==
Hi, I'm currently fixing Firefox that does not actually fire any onpuase/onresume events.

While fixing code, I noticed that the spec does not make it clear if `pause()`/`resume()` has to simply return `undefined` without firing an event, when its `state` is already `paused`/`recording`? Allowing them fire an event would cause duplicated events.

FYI, Chrome returns undefined at the very beginning when it is already paused/recording state.

Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/150 using your GitHub account
Received on Monday, 8 October 2018 23:02:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:07 UTC