- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Tue, 18 Jun 2013 00:02:04 +0200
- To: Martin Thomson <martin.thomson@gmail.com>
- CC: "public-media-capture@w3.org" <public-media-capture@w3.org>
On 06/17/2013 11:19 PM, Martin Thomson wrote: > On 17 June 2013 05:39, Harald Alvestrand <harald@alvestrand.no> wrote: > (trimming) >> One scenario I've heard (but which I don't think anyone's implemented yet) >> is that the user might switch cameras or microphones by some interaction >> with browser chrome rather than causing the application to getUserMedia >> again. I wouldn't be too concerned if that functionality were to go away - >> but again, I don't see a strong argument against it at the moment. > That is perfectly reasonable scenario. One that I might, as an > application developer be OK with allowing. > > But again, it's the user, not the user agent. I can't imagine > building a user agent that was inconsistent in this way. > > As I think more about this, it might be possible to set a sourceId > constraint after getting a stream. That might solve the problem. > Either way, there's something to do with the spec, even if it's just > informative. It seems to me that an example in the spec showing how to set a sourceId constraint using applyConstraints (if that is what we called it) after getting the stream might be sufficient to document how an app developer could indicate that it wants this behaviour. Do you want to write such an example?
Received on Monday, 17 June 2013 22:02:35 UTC