- From: Jim Barnett <Jim.Barnett@genesyslab.com>
- Date: Wed, 27 Nov 2013 14:32:11 +0000
- To: "public-media-capture@w3.org" <public-media-capture@w3.org>
Received on Wednesday, 27 November 2013 14:32:37 UTC
I am opposed to this. It makes the concept of 'mandatory' meaningless, and thus requires the app to examine every device it gets back to make sure that it actually meets the constraints. I do agree that unknown mandatory constraints should be treated somewhat differently, and think that there is a simple way to do this: in the case of an unknown mandatory constraint return an indication to the app (via the error callback) that the call failed because of an unknown mandatory constraint. Since the user has not yet been prompted at this point, the app can decide whether to give up silently or to remove the unknown constraint and try again. The app now has full control and can decide whether or not to ignore the unknown mandatory constraint. That's better than having the UA make that decision for it in a blunderbuss manner. - Jim
Received on Wednesday, 27 November 2013 14:32:37 UTC