W3C home > Mailing lists > Public > public-media-capture@w3.org > March 2016

[mediacapture-depth] Settings vs constrainable properties

From: Dominique Hazael-Massieux via GitHub <sysbot+gh@w3.org>
Date: Tue, 08 Mar 2016 14:54:09 +0000
To: public-media-capture@w3.org
Message-ID: <issues.opened-139297672-1457448849-sysbot+gh@w3.org>
dontcallmedom has just created a new issue for 
https://github.com/w3c/mediacapture-depth:

== Settings vs constrainable properties ==
The way Media Capture and Streams currently operates, the set of 
constrainable properties is the same as the set of settings obtained 
via getSettings().

This spec uses settings to report on non-constrainable properties.

That might be OK, but since that's clearly something that hasn't been 
done before, it would be good to check that this is consistent with 
the rest of the contrainable model.

Please view or discuss this issue at 
https://github.com/w3c/mediacapture-depth/issues/102 using your GitHub
 account
Received on Tuesday, 8 March 2016 14:54:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 8 March 2016 14:54:13 UTC