Confirmed users
113
edits
WebAPI/AudioChannels: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 236: | Line 236: | ||
* User lowers volume to a very low volume, this likely either affects content or ringer volume. Suddenly there's an incoming notification. However since this is a separate volume this can be very loud which is surprising to the user. | * User lowers volume to a very low volume, this likely either affects content or ringer volume. Suddenly there's an incoming notification. However since this is a separate volume this can be very loud which is surprising to the user. | ||
* User enters dialer and lowers volume. Then presses DTMF tone buttons and expects this to play at a low volume. | * User enters dialer and lowers volume. Then presses DTMF tone buttons and expects this to play at a low volume. | ||
=== Refactor Audio Channel Service === | |||
(3/20/2015 updated) | |||
* Gecko: The concept of refactoring the audio channel service is to deal with those issues that we couldn't solve by the existing mechanism in gecko, and we will need the changes(in below) in both gecko and gaia to have a new management. | |||
** '''New browser api''': {{Bug|1113086}} - this is the major part for the new browser api so that the gaia system app is able to control each iframe/app's audio channel, such as allowing or denying those types we have in b2g. | |||
** '''Telephony''': {{Bug|1129882}} - The new audio channel browser api will be implemented base on the foundation of media element, but the telephony api does not use media element to produce sound, so we need the telephony api to bind on a specific window(callscreen), just like the other apps did. | |||
** '''VOIP''': {{Bug|1126224}} - There will be 3rd party apps that use webrtc api to implement voip services, and to fit the ux spec, these apps might behave different from the gaia callscreen app, so probably we will need a new type called "voip" to distinguish from "telephony" and "voip" audio channels. | |||
** '''System''': {{Bug|1142933}} - The ux spec has specified a new audio channel type called "system" to represent those sounds that system use, such as the keyboard, screen lock or screenshot... | |||
* Gaia: The system app will use the browser api({{Bug|1113086}}) to control all the audio channels in gaia, it means we will move the audio channel service from gecko to gaia, since gaia has more window related information then gecko and can do a better management. | |||
** '''Audio Channel Manager''': {{Bug|1100822}} - we will introduce this new module in system app, to manage the audio channels. | |||
* UX: Before the refactoring started, developers and ux had meetings to discuss about the current audio issues and future needs, then came out a sound spec to define the audio channel behaviours. | |||
** '''Spec''': {{Bug|1068219}} - as the developers are implementing the new modules, meanwhile ux is also updating the spec if we encounter some problems on the behaviours or coding limitation. | |||
[[Category:Web APIs]] | [[Category:Web APIs]] | ||