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

These statements are not mutually exclusive. It seems some settings 
get applied during `takePhoto` and others get applied immediately. 
`zoom` seems to be in the latter cagetory, and seems no different from
 a constraint in this case.

Btw, this isn't about inability to satisfy, but about describing needs
 in an uncontentious, way. e.g. the comparison should not be with 
`getUserMedia` but with `applyConstraints`.

See applyConstraints in action in Firefox (which doesn't do any 
rescaling and is limited to a single shared native camera output)  in 
https://jsfiddle.net/ftdmdkjt/ - Try it in multiple tabs as well.

I don't think we can ignore adjacent tabs, as we're talking about a 
single shared hardware resource. We need to solve this because JS 
developers have no way to solve it.

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

Received on Friday, 16 December 2016 17:33:13 UTC