W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > February 2017

Re: [mediacapture-fromelement] define behaviors of the common ConstrainablePattern Interfaces

From: Miguel Casas-Sanchez via GitHub <sysbot+gh@w3.org>
Date: Fri, 10 Feb 2017 19:34:31 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-279043890-1486755270-sysbot+gh@w3.org>
To bring the Constrainable Pattern to the 
`CanvasCaptureMediaStreamTrack` and drawing from my experience with 
ImageCapture https://github.com/w3c/mediacapture-image/pull/146, I 
think roughly here we'd need to define a supported constraints 
dictionary as sth like:

partial dictionary MediaTrackSupportedConstraints {
 boolean width = false;
 boolean height = false;
 boolean aspectRatio = false;
 boolean frameRate = true;
 boolean facingMode = false;
 boolean volume = false;
 boolean sampleRate = false;
 boolean sampleSize = false;
 boolean echoCancellation = false;
 boolean latency = false;
 boolean channelCount = false;
 boolean deviceId = false;
 boolean groupId = false;

and also the behaviour of the rest of the Constrainable Pattern 
methods that are needed as well, i.e. these guys:

MediaTrackCapabilities getCapabilities ();
MediaTrackConstraints getConstraints ();
MediaTrackSettings getSettings ();
Promise<void> applyConstraints (optional MediaTrackConstraints 

And to round the change, `captureStream()` should accept a 
 a la `getUserMedia()`.

We should also have a similar analysis for the "standard" 
MediaStreamTrack produced by `captureStream()` on an HTMLMediaElement.

ImageCapture has a rendering of my proposed PR in 

GitHub Notification of comment by miguelao
Please view or discuss this issue at 
 using your GitHub account
Received on Friday, 10 February 2017 19:34:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:31 UTC