Use a mock WebAudioDevice only when testing

Use a mock WebAudioDevice only when testing

Currently when running the content shell a mock WebAudioDevice is used,
but the mock device should only be returned when we are testing.

BUG=none
R=pfeldman@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=261809

[elecro, 2014-03-13 17:43:40]

Original CL which introduced the mock WebAudioDevice:

https://chromiumcodereview.appspot.com/19023003

[elecro, 2014-03-17 16:36:26]

Added reviewers from the original patch.

[Avi (use Gerrit), 2014-03-17 17:56:50]

The code LG, but I don't know enough about this area to know if this is what we
want.

[jam, 2014-03-17 18:49:06]

this change looks fine to me, but before you can land it you need to go through 
http://dev.chromium.org/developers/contributing-code/#TOC-Get-your-code-ready

[elecro, 2014-03-18 09:03:57]

On 2014/03/17 18:49:06, jam wrote:
> this change looks fine to me, but before you can land it you need to go
through 
> http://dev.chromium.org/developers/contributing-code/#TOC-Get-your-code-ready

Okay, could you help me out here a bit: What am I missing? As far as I know I'm
on the Corporate CLA, I've created a review for adding myself to the AUTHORS
file (https://chromiumcodereview.appspot.com/195813006/) (maybe this shouldn't
be a separate CL?).

[elecro, 2014-03-27 12:16:55]

On 2014/03/18 09:03:57, pgal.u-szeged wrote:
> On 2014/03/17 18:49:06, jam wrote:
> > this change looks fine to me, but before you can land it you need to go
> through 
> >
http://dev.chromium.org/developers/contributing-code/#TOC-Get-your-code-ready
> 
> Okay, could you help me out here a bit: What am I missing? As far as I know
I'm
> on the Corporate CLA, I've created a review for adding myself to the AUTHORS
> file (https://chromiumcodereview.appspot.com/195813006/) (maybe this shouldn't
> be a separate CL?).

ping?

[elecro, 2014-04-03 16:19:25]

On 2014/03/17 18:49:06, jam wrote:
> this change looks fine to me, but before you can land it you need to go
through 
> http://dev.chromium.org/developers/contributing-code/#TOC-Get-your-code-ready

I'm in the Authors file, I've got CCLA, the style is the same as the other
methods, what am I missing here?

[piman, 2014-04-03 20:01:01]

On 2014/04/03 16:19:25, pgal.u-szeged wrote:
> On 2014/03/17 18:49:06, jam wrote:
> > this change looks fine to me, but before you can land it you need to go
> through 
> >
http://dev.chromium.org/developers/contributing-code/#TOC-Get-your-code-ready
> 
> I'm in the Authors file, I've got CCLA, the style is the same as the other
> methods, what am I missing here?

LGTM (I verified the CLA signers doc).

[elecro, 2014-04-04 12:16:01]

The CQ bit was checked by pgal.u-szeged@partner.samsung.com

[commit-bot: I haz the power, 2014-04-04 12:16:03]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/pgal.u-szeged@partner.samsung.com/1981...

[commit-bot: I haz the power, 2014-04-04 13:08:27]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-04-04 13:08:28]

Try jobs failed on following builders:
  tryserver.chromium on linux_chromium_chromeos_rel

[elecro, 2014-04-04 15:01:32]

The CQ bit was checked by pgal.u-szeged@partner.samsung.com

[commit-bot: I haz the power, 2014-04-04 15:01:51]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/pgal.u-szeged@partner.samsung.com/1981...

[commit-bot: I haz the power, 2014-04-04 15:29:45]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/pgal.u-szeged@partner.samsung.com/1981...

[commit-bot: I haz the power, 2014-04-04 18:53:19]

Change committed as 261809