- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Feb 2015 17:06:48 +0000
- To: public-media-capture-logs@w3.org
Works for me as well. I'm also coming around to Harald's point on perhaps having "exact" in ConstrainBooleanParameter, though how I got there is a bit convoluted: Reason A: I think "ideal' could make a lot of sense in getCapabilities() as a way to learn about things like native resolution, though I've been unsuccessful raising support for that. In any case, I observe that it would be hard to add things like that later if we go with plain values, since users would already be expecting plain values and would need to learn to expect something different. A dictionary on the other hand is easy to extend with future information. Reason B: It's a bit confounding that values returned in a dictionary may have different meaning if one were to pass it back to the UA. E.g. One might naively expect ..applyConstraints(alterSomeValues(getCapabilities())) to do something reasonable, but it wont if we return plain values in getCapabilities() (if we avoid plain values however then it works!) So @adam-be should we avoid returning plain values in getCapabilities? (we still want plain values in getSettings() I think, though one might make the same argument there). -- GitHub Notif of comment by jan-ivar See https://github.com/w3c/mediacapture-main/issues/138#issuecomment-74903114
Received on Wednesday, 18 February 2015 17:07:08 UTC