Re: Killing the Moz Audio Data API

2013-10-17 Thread Paul Adenot
Yes, I pinged him an hour ago, and he plans to replace all uses of Audio Data API by Web Audio. I think he posted in the bug. Paul. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Killing the Moz Audio Data API

2013-10-17 Thread Ehsan Akhgari
On 2013-10-17 10:06 AM, Benjamin Smedberg wrote: On 10/17/2013 2:28 AM, smaug wrote: On 10/17/2013 12:09 AM, Ehsan Akhgari wrote: I'd like to write a patch to kill Moz Audio Data in Firefox 28 in favor of Web Audio. We added a deprecation warning for this API in Firefox 23 (bug 855570). I'm n

Re: Killing the Moz Audio Data API

2013-10-17 Thread Ehsan Akhgari
On 2013-10-16 6:56 PM, Matthew Gregan wrote: At 2013-10-16T17:09:50-0400, Ehsan Akhgari wrote: I'd like to write a patch to kill Moz Audio Data in Firefox 28 in favor of Web Audio. We added a deprecation warning for this API in Firefox 23 (bug 855570). I'm not sure what our usual process for t

Re: Killing the Moz Audio Data API

2013-10-17 Thread Ehsan Akhgari
On 2013-10-17 9:29 AM, Andreas Gal wrote: Looks like the comms app has some residual use of the old audio API: apps/communications/dialer/js/keypad.js:this._audio.mozSetup(1, this._sampleRate); apps/system/emergency-call/js/keypad.js: this._audio.mozSetup(2, this._sampleRate); Should b

Re: Killing the Moz Audio Data API

2013-10-17 Thread Benjamin Smedberg
On 10/17/2013 2:28 AM, smaug wrote: On 10/17/2013 12:09 AM, Ehsan Akhgari wrote: I'd like to write a patch to kill Moz Audio Data in Firefox 28 in favor of Web Audio. We added a deprecation warning for this API in Firefox 23 (bug 855570). I'm not sure what our usual process for this kind of th

Re: Killing the Moz Audio Data API

2013-10-17 Thread Andreas Gal
Looks like the comms app has some residual use of the old audio API: apps/communications/dialer/js/keypad.js:this._audio.mozSetup(1, this._sampleRate); apps/system/emergency-call/js/keypad.js: this._audio.mozSetup(2, this._sampleRate); Should be easy to replace. I will file a bug and mak

Re: Killing the Moz Audio Data API

2013-10-17 Thread Benoit Jacob
The other day, while testing some B2G v1.2 stuff, I noticed the Moz Audio Data deprecation warning flying in adb logcat. So you probably need to check with B2G/Gaia people about the timing to kill this API. Benoit 2013/10/16 Ehsan Akhgari > I'd like to write a patch to kill Moz Audio Data in F

Re: Killing the Moz Audio Data API

2013-10-16 Thread smaug
On 10/17/2013 12:09 AM, Ehsan Akhgari wrote: I'd like to write a patch to kill Moz Audio Data in Firefox 28 in favor of Web Audio. We added a deprecation warning for this API in Firefox 23 (bug 855570). I'm not sure what our usual process for this kind of thing is, should we just take the patch

Re: Killing the Moz Audio Data API

2013-10-16 Thread Matthew Gregan
At 2013-10-16T17:09:50-0400, Ehsan Akhgari wrote: > I'd like to write a patch to kill Moz Audio Data in Firefox 28 in favor of > Web Audio. We added a deprecation warning for this API in Firefox 23 (bug > 855570). I'm not sure what our usual process for this kind of thing is, > should we just tak

Re: Killing the Moz Audio Data API

2013-10-16 Thread Ralph Giles
On 2013-10-16 2:26 PM, Anne van Kesteren wrote: > For obscure DOM methods we do the warnings, then give it a try in > nightlies and see if anyone screams. So yeah, you want to do that I > think. Sounds good to me. -r ___ dev-platform mailing list dev-p

Re: Killing the Moz Audio Data API

2013-10-16 Thread Anne van Kesteren
On Wed, Oct 16, 2013 at 10:09 PM, Ehsan Akhgari wrote: > I'd like to write a patch to kill Moz Audio Data in Firefox 28 in favor of > Web Audio. We added a deprecation warning for this API in Firefox 23 (bug > 855570). I'm not sure what our usual process for this kind of thing is, > should we ju

Killing the Moz Audio Data API

2013-10-16 Thread Ehsan Akhgari
I'd like to write a patch to kill Moz Audio Data in Firefox 28 in favor of Web Audio. We added a deprecation warning for this API in Firefox 23 (bug 855570). I'm not sure what our usual process for this kind of thing is, should we just take the patch, and evangelize on the broken websites enough