W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2019

[mediacapture-record] Why is start 5.3 in the specification? (#168)

From: guest271314 via GitHub <sysbot+gh@w3.org>
Date: Thu, 06 Jun 2019 15:55:54 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-453111712-1559836553-sysbot+gh@w3.org>
guest271314 has just created a new issue for https://github.com/w3c/mediacapture-record:

== Why is start 5.3 in the specification? ==
[start(optional unsigned long timeslice) ](https://w3c.github.io/mediacapture-record/#dom-mediarecorder-start)
> 3. If at any point, a track is added to or removed from the stream's track set, the UA MUST immediately stop gathering data, discard any data that it has gathered, and queue a task, using the DOM manipulation task source, that runs the following steps:
> 
>     1. Set state to inactive.
>     2. Fire an error event named InvalidModificationError at target.
>     3. Fire a blob event named dataavailable at target with blob.
>     4. Fire an event named stop at target. 

Why is the language of `start()` 5.3 (still) in the specification? 

- Why was recording multiple tracks _potentially of the same kind_ either not originally pursued to be specified, or attempted and not successful (technically)?

- Have we not _now_ advanced to the point where multiple tracks can be recorded?

Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/168 using your GitHub account
Received on Thursday, 6 June 2019 15:55:56 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 6 June 2019 15:55:56 UTC