- From: Adam Bergkvist <adam.bergkvist@ericsson.com>
- Date: Wed, 21 May 2014 15:29:17 +0200
- To: Martin Thomson <martin.thomson@gmail.com>, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- CC: Harald Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 2014-05-19 20:08, Martin Thomson wrote:
> On 19 May 2014 09:24, Stefan Håkansson LK
> <stefan.lk.hakansson@ericsson.com> wrote:
>> On 2014-05-18 20:47, Harald Alvestrand wrote:
>>> I'd like to have a real good story for why it shouldn't be an event
>>> fired at some object before introducing a third pattern in this API.
>>
>> The story would be precedence - watchPosition works this way. I don't
>> know if that is a real good story or not!
>
> watchPosition sets a bad precedent. I prefer using events.
>
I would prefer an event as well. The question is what object should be
the corresponding EventTarget.
I don't see that FF or Chrome have the
navigator.<prefix>getMediaDevices() function yet. It would be nice to
have some object on navigator where we could isolate our new stuff which
also could be our EventTarget.
navigator.userMedia.getMediaDevices(...);
navigator.userMedia.ondevice = function (evt) { ... };
/Adam
Received on Wednesday, 21 May 2014 13:29:44 UTC