WebAPI/AudioChannels: Difference between revisions

WebAPI/AudioChannels (view source)

4 bytes removed , 21 April 2015

Confirmed users

381

edits

@@ Line 238: / Line 238: @@
 === Refactor Audio Channel Service ===
-(04/09/2015 updated)
+(04/21/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.
@@ Line 251: / Line 251: @@
 * 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.
-*** The 2nd round review is done, Evan is addressing the issues we found in the offline discussions, after that he will work on the tests.
+*** Patch is still on review process. Tests are added, and the CI is good.
+*** We're doing our best to land the patch this week. GOGO!
 * 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.