** Tags removed: rtm14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1329085
Title:
unexpected audio policy user experience
To manage notifications about this bug go to:
Media-hub can only be involved in this once the browser is actually
using it when playing audio/video. The main problem we have atm is that
the browser is talking directly to pulse, and not going via media-hub,
so there's no simple way for the app to know that it has to stop/pause.
** Changed in:
this isn't a webbrowser bug either way though. there are separate bugs
filed to have browser use media-hub but that's not the condition you are
describing.
** Also affects: media-hub (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
sounds like you are looking for a way for the media-hub to add some
policy around requests being made to it from multiple streams. will add
a media-hub task for it.
** Changed in: webbrowser-app (Ubuntu)
Status: New = Invalid
** Changed in: webbrowser-app
Status: New = Invalid
--
It can't be rtm14 as far as i can tell.
The problem is that MH does not have a way AFAICT of letting an app express the
type of audio environment it wants.
So it mostly multiplexes stuff it receives.
There is no way either, and rightfully so, of stopping a stream from an app,
unless it's your
the tag is really a suggestion, i think this is one of those bugs on the edge,
i could see it argued in or out of rtm.
worthy of some LT discussion imho.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: webbrowser-app (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rtm14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1329085
Title:
unexpected audio policy user
