Revert the mute button behavior from v136

[codereptile]

Please revert the mute button behavior introduced in v136. This breaks the existing workflow and it an unwelcome change! I know about the userChrome.css workaround - but it's a workaround to something that should not have been implemented in the first place. Instead of switching to the tabs, existing user constantly mute them, or close them if the audio happens to stop when I'm trying to click (eg clicking on tab after a notification sound). How was such a breaking mechanic introduced without any experiment to see if people actually want it?

[siffemcon]

You should also post that at https://connect.mozilla.org/t5/ideas/idb-p/ideas.

[rosencraft]

I completely agree, especially in vertical tabs this function has not been tested enough. The user keeps muting/unmuting the tab instead of switching to it. Please at least put an option in about:config to disable the ability to press on the button (leaving it there just to say there is sound coming from that tab)

[Agentvirtuel]

Hello

Of course, this is not the expected answer, nevertheless, for information purposes.

https://connect.mozilla.org/t5/discussions/help-the-mute-button/m-p/108096/highlight/true#M41664
You can use a userChrome.css file to hide button

And you can use Tab overview menu for searching for a tab producing sound.
https://support.mozilla.org/en-US/kb/tab-overview-menu