[Bug] Child tabs don't mute on parent mute if not playing sound

[rixx]

[Bug] Child tabs don't mute on parent mute if not playing sound

[piroor]

I'm negative to change the behavior of the "sound playing" icon on TST tree items.

Behaviors of the sound playing button and "Mute/Unmute Tab" context menu commands on Firefox's native tabs are:

1a. "Mute/Unmute Tab" context menu commands affect to the target tab whether the tab is sound-playing or not.
2a. The sound playing button is shown on a sound playing tab. Clicking on the button mutes the tab, and clicking again unmutes the tab.
3a. On recent versions of Firefox, the button is shown on "ready to play sound" tabs (e.g. YouTube tabs opened in the background) also. Clicking such a "ready to play" button starts playing sound of the tab.

On the other hand, the sound playing button and "Mute/Unmute Tab" context menu commands in TST are:

1b. "Mute/Unmute Tab" context menu commands affect to the target individual tab whether the tab is sound-playing or not. This is compatible to Firefox's native commands.
2b. The sound playing button is shown on a sound playing tab or the parent of a collapsed tree containing sound playing descendant. Clicking on the button mutes the sound playing tab, and clicking again unmutes the tab.
3b. "Ready to play sound" button never appear on TST tabs because Firefox does not expose such a state of tabs to addons via WebExtensions API.

The actual result you saw is from the behavior 2b. It is by design. I think it is most natural behavior of the button on TST's tree because the sound playing button on Firefox's native tabs does not provide ability to mute non-sound-playing tabs.

However I agree that there is demand to mute whole tree. Thus I've added new context menu commands "Mute/Unmute this Tree" and "Mute/Unmute Descendants". I hope these commands help you.

[rixx]

Thank you, yes, that added context menu will do the trick.

Just to explain my original reasoning (and why I still think that the behaviour is bug-alike, but certainly not a priority to fix): I think the discrepancy in expectation comes from the fact that you can mute a tab with Ctrl-m at all times, so I never use the actual button, and I was confused when two actions that have the same result in vanilla (button click / C-m both mute a tab) did not have the same result in TST.

[piroor]

Thank you for explanation!

Ctrl-M is processed by Firefox itself and it corresponds to the "Mute/Unmute Tab" command in the context menu. When you mainly see TST's sidebar, it works like as "Mute/Unmute the active individual tab". I also introduced keyboard shortcut slots for newly added commands so using them instead of Ctrl-M may reduce confusions like yours.