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

[mediacapture-image] Use the constrainable pattern instead of creating a subtly different function set

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Wed, 07 Dec 2016 12:21:13 +0000
To: public-media-capture@w3.org
Message-ID: <issues.opened-194035498-1481113271-sysbot+gh@w3.org>
alvestrand has just created a new issue for 
https://github.com/w3c/mediacapture-image:

== Use the constrainable pattern instead of creating a subtly 
different function set ==
The combination of getPhotoCapabilities (with both ranges and current 
settings) and setOptions creates an almost equivalent set of 
functionalities to the constrainable pattern used on MediaStreamTrack.

Two nearly identical patterns is a bad thing for the platform. Please 
reconsider.

(This has been discussed before, and I know giri does not agree with 
me. I wish for the discussion to be recorded as a top-level issue in 
this tracker.)


Please view or discuss this issue at 
https://github.com/w3c/mediacapture-image/issues/124 using your GitHub
 account
Received on Wednesday, 7 December 2016 12:21:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 December 2016 12:21:19 UTC