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

@jan-ivar 
No, I don't believe this is the same form of contention.  If the 
underlying implementation (HW + platform + UA) cannot satisfy cannot 
satisfy a setOptions() call at a given instant in time for one webpage
 because another webpage had invoked setOptions() on a mediaStream 
with the exact same setting (in this case zoom) at the same time, then
 that webpage can always implement its own logic to try to apply the 
setting after some delay.  

What is the likelihood of two webpages in the active browser context 
trying to apply overlapping photo settings at the same time?  If we 
think it is going to be a rare event, then constraints seems to be 
overkill to solve this problem.  


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

Received on Friday, 16 December 2016 00:06:02 UTC