- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Sep 2016 10:16:59 +0000
- To: public-media-capture-logs@w3.org
Hmm..... would the following work? somewhere under "operation": "When external events happen that cause the UA to desire a change to the settings of a track, the UA can run the Select Settings algorithm again and apply the results at any time. If this results in not being able to satisfy the constraints, the UA MUST fire the "overconstrained" event." "Examples of things that might cause such events are lightning condition changes, network congestion, capture devices being shared by other tracks, or ...." (For consistency, we should start sending black/silence when this happens. I don't think that's very user-friendly, however - sending out-of-constraints results might be more useful for the user.) -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/360#issuecomment-245555016 using your GitHub account
Received on Thursday, 8 September 2016 10:17:06 UTC