- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Thu, 10 Apr 2014 15:32:09 +0200
- To: public-media-capture@w3.org
Taking discussion to the list, because of my dislike for cluttering bugs
with he-thinks/she-thinks:
The use cases for exposing the number and ID of devices I remember are:
- When no devices of a class are available, the app can choose not to
display relevant UI components at all (don't put up a self-view if you
have no camera).
- When one device is available, device-choice functions in the UI can be
hidden.
- When multiple devices are available, exposing the ID enables the app
to distinguish clearly between the "I have seen this device before" use
case and the "All devices are new to me" use case.
I don't think these scenarios are new to anyone here.
On 04/09/2014 07:57 PM, bugzilla@jessica.w3.org wrote:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=25245
>
> --- Comment #7 from Martin Thomson <martin.thomson@gmail.com> ---
> (In reply to Jan-Ivar Bruaroey [:jib] from comment #6)
>> (In reply to Martin Thomson from comment #5)
>>
>> That seems doable without this feature. gUM({sourceId:x}) fails == n/a
>> detected.
> True, for this case. As long as you make it fail hard, gUM won't trigger the
> user prompt. That's not true of some of the other use cases. I know that I
> shouldn't have trouble summoning the details, but I am. I'll have to get back
> to this.
>
> "group" allows an application to select a paired camera and microphone. It
> also prevents cases where audio output is directed to one set of headphones,
> and input is derived from the same.
>
Received on Thursday, 10 April 2014 13:32:38 UTC