Unexpected Behavior: Video Auto-Plays Muted Without Prompting for Permissions

[migolo]

We’ve recently encountered unexpected behavior in some of our videos across different browsers.

🔗 Reproduction Example:
JSFiddle Demo

⸻

Expected Behavior

When a user lands on the page:
1. The video player should attempt to play with sound.
2. If autoplay with sound is not permitted (due to browser autoplay policies), the browser should:
• Fail gracefully with an error we can catch and handle (e.g., showing a “Play button to gather permission” overlay or similar UX).

⸻

Actual Behavior

Currently, the video auto-plays muted without any user interaction or prompt.
This occurs even when autoplay with sound fails, and we never receive a clear signal that permission is needed.

⸻
Steps to Reproduce
1. Open the JSFiddle.
2. Observe that the video auto-plays muted.
3. No prompt or interaction is required or requested by the browser.
4. No error is thrown or caught in our code.

⸻
Notes
• We’ve confirmed this behavior in Chrome and Safari (latest versions).
• We’re explicitly setting .muted = false and calling .play() programmatically.
• We suspect this may be related to browser autoplay policies, but we want a way to detect or intercept this fallback behavior so we can prompt the user manually if needed.

[rkrishnan8594]

We recently updated the player to continue playing the video in a muted state if unmuted playback is blocked by the browser. We could look into emitting an error event in this case, while still playing the video. You could listen for the error and pause playback in order to prompt the user to unmute the player. Would that handle your use case?

[migolo]

Thanks for the clarification, Rowan!

Is there currently a flag or configuration that would allow us to opt into the previous behavior (i.e., prevent playback entirely if unmuted autoplay is blocked)?

If not, then yes—having a reliable way to detect this scenario would definitely help.

Let us know what you think is the best path forward. Thanks again!

[rkrishnan8594]

@mcintyrehh had a good suggestion - you could listen for a play or timeupdate event, and if player.getMuted() resolves with true, you could call player.pause() and prompt the user to unmute the player. You'd only want to enable this behavior on unmuted autoplaying videos.

[migolo]

Thanks for the suggestion! I’ve updated the fiddle here:
🔗 https://jsfiddle.net/48urx72f/2/

In this example, the video is being played as a direct result of a user interaction (player.play() is triggered by a click event). We also call player.setMuted(false) immediately after.

However, the video still plays muted, and player.getMuted() returns true during the play event. This causes our check to fail, even though the user explicitly initiated playback.

So even when we’re not relying on autoplay, the player ends up muted and we can’t distinguish whether:
• The browser forced muted playback, or
• The mute state was applied by the player internally.

This makes it hard to implement the workaround reliably, since we can’t detect when the mute was enforced versus intended.

Would love to know if there’s:
1. A flag or way to disable this new fallback behavior for muted playback.
2. Or a more deterministic event or signal we can hook into to identify this case clearly.

Thanks again for the help!

[rkrishnan8594]

I haven't been able to reproduce muted playback on that JSFiddle, but if it's occurring, it's because the browser muted the player, so you can display your prompt to the user.

[migolo]

That is weird, I am unable to play the video at all (given that is muted) with the rule you mentioned, the play button is setting the muted to false.
https://github.com/user-attachments/assets/31feec77-f556-4513-82ec-a3ab100732c0