Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Volume slider 'contracts' to mute/unmute button when audio file over 1h

  • 4 uphendule
  • 1 inale nkinga
  • 143 views
  • Igcine ukuphendulwa ngu Denys

On various websites with embedded podcasts, when the file goes past 1h the volume 'slider' goes away and becomes a basic mute/unmute button. How can i force Firefox to always display the volume slider?

On various websites with embedded podcasts, when the file goes past 1h the volume 'slider' goes away and becomes a basic mute/unmute button. How can i force Firefox to always display the volume slider?
Ama-screenshot ananyekiwe

All Replies (4)

Hi,

Does the issue persist in other browsers (such as Chrome, Edge, Opera or Safari)?

Also, could you please give the URLs of some of such websites?

Here's an example: https://boardgamegeek.com/boardgamepodcast/25985/shut-up-and-sit-down

The 2024’s Best Games podcast down the page which is the longest at 1:03h triggers the 'shortening' of the volume bar, everything else has the volume slider. Another example more clearly here: https://boardgamegeek.com/boardgamepodcast/25780/adeptus-podcastus

In Edge for example, the UI is different, with hover-over the volume/mute button reveals a volume slider to the left 'over' the scrubbing timeline, and is consistent across all lenght implementations.

Thank you for giving the examples, that's definitely a compatibility issue. I've been able to reproduce it and have reported it on Webcompat. The team will look into it, and I'll keep you updated.

As a temporary workaround, you can right-click the audio control, select Copy Audio Link from the context menu and open it in a new tab.

I've also reported it on Bugzilla, so that it sooner reaches the right team.