Re: [mediacapture-main] How to handle known but unsupported constraints

I think there is value in having UAs not return `true` in 
supportedConstraints until they can reliably implement it. The reason 
is that for a constraint `foo`:

As a web-dev, if browser X returns `false` in supportedConstraints 
then I know the browser does not support it, and I can tell the user 
their browser is the problem, not (necessarily) their hardware.

If browser X returns `true` in supportedConstraints but then I get a 
single zeroish value in all getCapabilities(), then it would be nice 
if I could assume that the browser does support it, and I could 
unequivocally tell the user their browser is fine, but that they need 
to run out and buy more hardware.


-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at 
https://github.com/w3c/mediacapture-main/issues/296#issuecomment-173726112
 using your GitHub account

Received on Thursday, 21 January 2016 22:08:41 UTC