Closed Bug 1440971 Opened 7 years ago Closed 4 years ago

Short audio crackle from unfocused tab

Categories

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

58 Branch
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: wingtree6, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0 Build ID: 20180206200532 Steps to reproduce: Open the following link a new tab and don't switching to that tab: https://www.shadertoy.com/view/4tjGRh Actual results: After the page loads, a short crackling sound is heard from the video playing. Expected results: The video/audio should have started playing only after I switched to that tab.
Summary: Short audio crackle in unfocused tab → Short audio crackle from unfocused tab
Component: General → Audio/Video: Playback
Product: Firefox → Core
Sounds like a job for block autoplay?
Priority: -- → P3
Sort of. Looks like shadertoy lets you generate audio waveforms in webgl and then handles playing them. I don't see any media elements in the about:media devtools panel, so presumedly it's using webaudio for the actual output. So the user experience is the same as with an autoplaying video in an untouched tab, but the mechanism is different. What do you think about handling this, Chris?
Flags: needinfo?(cpearce)
At least the tab mute button works in this case.
This is an artefact of how we do the delay playback start until tab focus. It would be a big job to rework that. Block autoplay would help here.
Flags: needinfo?(cpearce)
I guess we could crossfade when switching to the tab? That's still a fair bit of work. Hopefully the situation will improve with autoplay blocking, scheduled to ship later this year. Until this there's probably not much we can do. Thanks for the report though. Neat demo!
Priority: P3 → P5

Tested on Firefox 89.0.1 (64-bit) on Windows 10 and the issue is resolved with the tab showing up as "AUTOPLAY BLOCKED".

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.