On Tue, Oct 30, 2012 at 4:43 PM, Timothy B. Terriberry < [email protected]> wrote:
> This is what happens if you mute the audio output, instead of stopping it. > I think Rob was suggesting actually stopping it (which would appear no > different to the app than if the user clicked pause). > Right. As for a "playOne" attribute, or whatever you want to call it, part of the > problem for WebRTC at least is that there may be multiple media elements > involved in a single call (especially a multi-party video call). That may > not matter for the B2G case, but I think we should at least consider the > WebRTC case, as we may want something we can re-use for both cases, rather > than multiple non-generic mechanisms. Good point. That's a good argument for just dispatching events and letting the application take care of stopping and starting playback. Rob -- Jesus called them together and said, “You know that the rulers of the Gentiles lord it over them, and their high officials exercise authority over them. Not so with you. Instead, whoever wants to become great among you must be your servant, and whoever wants to be first must be your slave — just as the Son of Man did not come to be served, but to serve, and to give his life as a ransom for many.” [Matthew 20:25-28] _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
