Chairs' notes from the Media Capture TF Meeting, May 19

In the interest of speedily agreeing that we have captured the high 
points of decisions, here's our collected notes from the Media Capture 
TF meeting May 19 (with followups on 20 and 21), as seen by chairs. This 
does not constitute minutes, it's the chairs' summary of decisions.


Bug walkthrough. Individual dispositions:

* 22214 How long do permissions persist?
Needs more discussion.
* 22337 When does the light come on?
Agreement that there are 2 different indicators - “have permission” and 
“recording”
Both need to be visible to the user. Slow decay of “recording” is good 
(this is implementation advice).
* 25707/25708 Async getSettings?
Agreement to close as “no change needed”
* 23820 Special values in constraints
Subsumed into “ideal” discussion and constraints reworking
Consensus that “ideal” looks like a promising thing to do inside 
constraints.
* 25298 FacingMode value of “other”
Agreement that JS “undefined” should be used for other/unknown
Agreement that DOMString needs to be used rather than enum in the formal 
WebIDL,
because enums don’t allow defaulting (yet).
Jan-Ivar took on working out a text proposal.
* 25247 GetCapabilities without a track
As stated, “won’t fix”.
* 24015 Event to signal when devices have changed
Agreement that such an event is needed.
(Later) suggestion to add a Navigator.mediaDeviceHandler object that the 
event could be fired at.
AdamBe took on flushing out a complete proposal.
* 23128 “get access” call
No support for reopening. Remains closed.

Recorder review. Agreement that at least target bitrate, media type and 
seekability (keyframe interval)
needs to be given to the recorder as parameters at startup. These can’t 
be represented as track constraints.
Agreement to remove “warning” event (and “onwarning”). Otherwise, “looks 
good”.

Capture MediaStream from media element: people liked this. Not 
controversial.
Clarifying things like tracks of resulting MS (max one audio and one video,
representing mix of all played audio tracks and the selected video track 
respectively).
Show of hands indicated a preference for having it in the gUM draft (not 
a separate doc).

Followups concerned the "constraints" format.

On Tuesday: Consensus for removing “required:” field and putting 
"required" flags into individual units

On Wednesday: Consensus for a model where “exact”, “max” and “min” 
values are always mandatory,
“ideal” is always optionalish, and a naked value means “ideal”.
Peter to draft a proposal (“pull request”?) by June 7.

Consensus that “advanced” will be part of the proposal going forward.

Received on Tuesday, 27 May 2014 13:28:06 UTC