- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Fri, 30 Jan 2015 13:36:46 +0000
- To: public-media-capture-logs@w3.org
There's no order determinism whatsoever. The UA (and ultimately the user) may arbitrarily reject or allow either or both or neither call, and do so in any order. Why is this a problem? Also, a spec cannot outlaw apps making calls, people will make calls. All it can do is mandate an implementation outcome. However, even if there's a problem here, I fail to understand the prescription: how will outlawing two compatible calls from succeeding have any effect on how two incompatible calls behave where both cannot obviously succeed, other than to make more of them by effectively making all subsequent calls into incompatible calls? It is up to the UA how to resolve conflict in constraints when sharing capture devices, whether from different tabs or from consecutive getUserMedia() calls. I don't see a problem with that. -- GitHub Notif of comment by jan-ivar See https://github.com/w3c/mediacapture-main/issues/67#issuecomment-72201206
Received on Friday, 30 January 2015 13:36:55 UTC