On Fri, Nov 30, 2012 at 5:48 AM, Henrik Skupin <[email protected]> wrote:
> Henrik Skupin wrote on 11/30/12 2:41 PM:
>
> > {picture: true, audio: true}
> > {picture: true, video: true}
> > {video: true, audio: true, picture: true}
>
> Also why does `mozGetUserMedia(1, function() {}, function() {}' throw
> instead of calling the onErrorCallback as given by the spec? I haven't
> tested yet how Chrome handles that but if we decide to take another
> route as given by the spec we will indeed cause trouble by developers
> who want to use this feature.
Actually, the WG isn't completely clear on this point. There is some
feeling that simple programming errors (like the one you illustrate
above) should just throw exceptions.
> Also what is the reason why the onErrorCallback is mandatory in our
> implementation while the spec says it's optional?
>
We decided to make it mandatory at the most recent TPAC. The
spec is out of date.
> I would love if we can document anything we implement differently. If we
> don't do this it will be hard for everyone to get started.
Why don't you record these issues somewhere and then when things
stabilize, we can figure out which ones are really variants and need
real documentation.
-Ekr
-Ekr
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
