927347 - [B2G] Oscillator node keep making sound on homescreen

Status: RESOLVED DUPLICATE of bug 927322

(Core :: Web Audio, defect)

Description

[Paul Yang [:pyang] (away)]

Use device: buri/unagi
Prerequisite:
- Access http://zapion.github.io/webaudio/oscillator.html

STR:
1. Start oscillator node by play button
2. Press home key (oscillator page moved to background)

EXPECT:
- oscillator stops

ACTUAL:
- It keeps making sound.

Comment 1

[Jason Smith [:jsmith]]

There's no audio channels hooked up on that test page, right? If so, this is incorrect behavior on Firefox OS. By default, sound is supposed to only play in the foreground app by default when the test page has no audio channel types applied. Moving the app to the background should result in sound not playing with an app with no audio channel types applied.

Comment 2

[Paul Adenot (:padenot)]

This might be fixed by bug 927322.

Comment 3

[(no longer active)]

Yeah, Paul (Yang), can you please try with the patch in that bug?

Comment 4

[Paul Yang [:pyang] (away)]

Webaudio support only audio-normal so it should be played foreground.

(In reply to Jason Smith [:jsmith] from comment #1)
> There's no audio channels hooked up on that test page, right? If so, this is
> incorrect behavior on Firefox OS. By default, sound is supposed to only play
> in the foreground app by default when the test page has no audio channel
> types applied. Moving the app to the background should result in sound not
> playing with an app with no audio channel types applied.

Comment 5

[Jason Smith [:jsmith]]

Sounds like this should block then - that means audio channel integration isn't working correctly for the normal channel with web content.

Comment 6

[Maire Reavy [:mreavy]]

Paul (Yang) - Have you had a chance to try this test with the patch from bug 927322? (See Comment 3 and Comment 4.)  Thanks.

Comment 7

[Paul Yang [:pyang] (away)]

Thanks for Jw's help, the patch from bug 927322 can solve.

Comment 8

[(no longer active)]

(In reply to Paul Yang [: pyang] from comment #7)
> Thanks for Jw's help, the patch from bug 927322 can solve.

Thanks!  Marking this as a dupe then.  I landed the patch on that bug on inbound just now.