Separate Firefox Autoplay Blocking From a Video Playback Fault
A video that waits for a click may be following the browser’s autoplay rule. That is different from a video that cannot play at all. Before changing speakers, reinstalling drivers or allowing every site to make noise, test the player’s own Play control.
Establish the manual-play result
Open a harmless clip on the affected training site. Press Play and check that the picture advances and any expected sound is audible. Note whether the only missing behaviour is an automatic start when the page loads.
Firefox blocks media with sound from autoplaying by default. It also offers a stricter Block Audio and Video setting, including muted video. Look for the autoplay-blocking indicator in the address bar when the site attempts to start its media.
If manual playback fails too, preserve that observation. Autoplay permission does not by itself diagnose a network interruption, unsupported media or an audio-output problem. Report the player message and whether another clip on the same service plays.
Choose a scoped preference
If automatic playback is useful for the verified site, use the site-information control to change its autoplay setting. Keep the general preference separate. A training platform’s requirements do not establish a need for unrelated websites to start audio immediately.
Reload the same harmless clip and check the expected automatic behaviour. Then return to manual operation or remove the exception if it provides no benefit. Save changes in the Autoplay settings list when managing existing entries.
For shared or quiet workspaces, consider whether manually pressing Play is actually preferable. A predictable start gives the user time to select headphones and check volume. Record the chosen site rule so that another person does not mistake an intentional block for a broken computer.
The useful result is clear: manual playback works, the site-specific autoplay preference behaves as selected, and any remaining playback failure has its own evidence rather than being hidden by a broad permission change.
Sources: Mozilla Support.