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?
