Closed Bug 1100771 Opened 10 years ago Closed 6 years ago

The |playing| event does not fire every time after the paused audio element was resumed

Categories

(Core :: Audio/Video: Playback, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: dkuo, Unassigned)

References

Details

This is an issue found in firefox os gaia's music app, in the music app, we listen to the audio element's |playing| event[1] to set the player's playback status, and bug 1082938 has found the |playing| event does not fire every time(after the bluetooth headset is disconnected), I am not sure if the bluetooth step is related, just highlight it cause it seems the only difference comparing to the normal usage of the audio element in the music app.

Actually the music app also listen to the |play| event[2] to change the playpause button's state, probably I have misunderstood the usage of the |playing| event and I should use the |play| event instead? (I already did it because it fires as we expected, every time after we call audio.play())

[1] https://developer.mozilla.org/en-US/docs/Web/Events/playing
[2] https://developer.mozilla.org/en-US/docs/Web/Events/play
'playing' will not always fire if decoding is slower than consuming. What is 'playing' event for in the music app?
(In reply to JW Wang [:jwwang] from comment #1)
> 'playing' will not always fire if decoding is slower than consuming. What is
> 'playing' event for in the music app?

The music app has several playback states and one of them is called "PLAYING", this state means the music player is in the playing state, so the music app listen to the audio element's "playing" event then set the playback state to "PLAYING" if it fires.
See http://dev.w3.org/html5/spec-preview/media-elements.html#mediaevents.

I think the definition of 'playing' of music app is slightly different from that of an media element. For music app, the state is 'playing' after the play button is clicked, right?
Component: Audio/Video → Audio/Video: Playback
Mass closing do to inactivity.
Feel free to re-open if still needed.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.