"Mute site" means "mute site", not "mute tab".

Working as designed.

Can we please look into this? Mute tab is infinitely more useful for me.

What sorts of use cases make "mute tab" more useful to you?

When I wanted to look at multiple pages on a site, both that played audio (lets say twitch streams)

It's much easier to use the old mute tab feature while switching between tabs. Having to actually mute the player is significantly out of the way.

In fact, that's all I used it for. I might as well disable mute site flag it is so useless to me.

Okay, looking at the source code, the tab muting still exists. Turning on enable-tab-audio-muting and disabling sound-content-setting will restore this into a useful feature.

 Issue 806991  has been merged into this issue.

> Okay, looking at the source code, the tab muting still exists. Turning on 
> enable-tab-audio-muting and disabling sound-content-setting will restore this 
> into a useful feature.

Please, do not do that, we will remove this flag one day and it will break you. However, extensions can mute tabs individually, you might want to explore this route.

+johnpallett@ FYI

Should not need an extension to correct this behavior. This is inappropriate. 

Another use case where Mute Tab is useful:
When I have gmail tabs for multiple accounts, or multiple slack tabs or other similar sites, I sometimes temporarily mute a tab say with a particularly busy chat that triggers too many notification sounds but still need to be able to hear notifications from the other accounts. It's easier for me to just mute the tab that's being too noisy rather than go through the sound settings for the particular web applications in those tabs, settings that I might forget to revert and later miss out on notifications.

 Issue 816319  has been merged into this issue.

I see my post was merged here so I just wanted second the use cases mentioned by the original poster here.  I'd add that I'm honestly trying to think when "Mute Site" would be helpful and I can't think of one use case that would make this superior to "Mute Tab".

there's no reason for the original behavior to have been changed to apply to an entire domain. specifically, if there's no way to edit the filter used, it's actually a useless feature - say I want to mute x.domain.com AND y.domain.com - "mute site" won't work!

bring back "mute tab"

How is this still being argued about? Fix this, please. 

Mute Tab for me is also far more useful than Mute Site. Also, why remove Mute Tab at all. If you're going to add Mute Site, just put it below Mute Tab. It's not as if there's no room in the tab contextual menu for more commands. Don't take away useful functionality just because you prefer another function.

AFAIK there aren't current plans to change this back, but I appreciate the use cases cited in comments 4 and 9, as those might help inform future direction here.

Site-muting functionality is intended to deal with troublesome/annoying sites rather than serve as a frequently-toggled button.  Tab-muting functionality serves a distinct set of cases and is available via the extensions API, so I suggest finding/building extensions that provide easy per-tab muting controls.

@12: You should be able to control specific hosts versus domain subtrees by editing/adding/removing patterns at chrome://settings/content/sound .

@14: There are code and UI difficulties providing both functions simultaneously; it's not just being arbitrary.

Ridiculous. I still don't understand the intentional obtuseness to justify removing a feature that was used by many people as dealing with troublesome sites. I've made the switch to Opera on my home machines and will be slowly moving to something else at work....over this one bug! 

@15 Please reconsider, here's why:

Tab muting is an effective way to deal with annyoing or troublesome sites for most usage, and has been used this way *in addition* to the cases we described.
Site-wide muting on the other hand, serves a special case where one has many tabs open for the troublesome site and it's cumbersome to individually mute them or when one doesn't want to hear things from that site again. It's a welcome addition for when the regular method is not enough, but not a real replacement, one is an individual operation the other one in bulk.
Compare this to the Close Tab vs Close Other Tabs. Close tab (be it via menu or the X or middle-clicking) is by far the most commonly used function, although I appreciate and am thankful for the occasions where I've had to use the special cases. It would not be reasonable to get rid of Close Tab and push it to extension space and just leave Close Other Tabs for instance.

I understand there might be challenges to have both, as you say in UI and code, but the solution is not to nuke the current functionality, but rather to fix those issues and when they are fixed implement the Mute Site properly.

 Issue 818477  has been merged into this issue.

over 3k views on this topic:
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/chrome/UxeVWuLjNAk/q_nxPSt8AAAJ

As well as fielding numerous questions from users in person, this is easily categorized as an *issue*. In my experience, many prefer the mute-tab option, but would also welcome the ability to additionally mute certain sites.

A few reasons:
Pre-muting tabs. User has desired audio playing on one tab (Tab A), wants to browse noise free in another tab. They don't necessarily know which sites they'll be visiting yet, nor if they will, or will not make noise. This may even include browsing a different page on the same site as Tab A.

Multiple tabs, same site, 1 desired audio source.

There are times where users want to mute a site, but only for the duration of the tab. There's no desire for the mute to last beyond their current session.

Users want to mute a tab on their desktop, while leaving an oft-used site open on it for ease of access. They're actively using their laptop, and want the laptop to generate noise from said site. 
Signed into chrome on both machines with mute sites? both make noise, or both do not.

I wanted to add to this,

Without re-enabling this feature, or at very least continuing to allow re-enablement through flags, users are being actively encouraged to seek out an extension, wading through the related security risks in doing so.

By forcing users to select an extension, there's a good possibility of a user downloading malware.

To this end it is a rampant enough issue that searching "mute tab removed" brings up many pages on how to remove said malware.

Assuming January 24th or thereabout was when this was released to a broader audience, perhaps this google trend data may add some objectivity...

Deleted: mute tab trends after removed.png 66.0 KB

	mute tab trends after removed.png 66.0 KB View Download

Mute Site, although useful under some circumstances, is not a replacement for mute tab, and never should be.  The thinking behind Mute Site seems to be that although the browser supports multiple tabs, no one would ever use multiple tabs for the same site. That's ridiculous.

I use multiple tabs for the same site, and in some cases want to mute some of the tabs for that site, but not all of them. I welcome Mute Site as an additional feature, but it is not a replacement for Mute Tab. Please don't remove the Mute Tab functionality in the future, and bring it back by default in the same fashion as what happens currently when Mute Tab is re-enabled via the flags settings. 

I have no use for mute site feature, but a lot of use for mute tab. I often have multiple streams open from the same site and mute tab has been very useful for me. At least leave the flag option, it has been there for years, why remove it now?

You want to add a probably useless feature? Fine. I guess a handful of people on the planet will find "mute site" useful. But why do you have to remove the old, well established, obviously useful one? Can't you just keep both?

I wonder what will be next: will they replace "close tab" with "close site", which will close all tabs and windows from the same domain?

(that's another thing by the way, calling a domain a "site", ridiculous...)

A step backwards, it makes no sense. please think about reverting this change. 

This is a horrible design change!

Why should your options be limited to a complete mute-all-tabs-from-one-site or not option?

I honestly see very little reason for this failure in work flow analysis. Meanwhile, there are so many reasons for muting only one or all but one tab from a site. 

This is why you need to pay attention to how a feature is used by users, not just the engineers...

I too frequently have multiple twitch streams open and the mute tab function was incredibly useful :(

Really is a shame that the Chrome team have made their decision with this and have no plans to fix it. Why remove such a useful function? Makes no sense.

Please don't remove the mute tab, I use it a lot and looking at the comments here it seems that I'm not alone. The "mute site" feature might be a good addition but not at the expense of "mute tab".

Who can we report inappropriate behavior of the dev's assigned to this issue to? This is ridiculous and asinine just to stroke some UI dev's ego (I won boys! The users hate me!). 

Please keep discussions respectful and constructive. See our code of conduct. 

https://chromium.googlesource.com/chromium/src/+/master/CODE_OF_CONDUCT.md

In my opinion mute tab is more than likely what people want instead mute site, or show both options.

Another Use Case: We (used to) use Mute Tab regularly with Google Meet when working from home so that we could join the meeting twice in two different windows on two different screens so that we could see the screenshare in one window and the video feed in another window. But we had to mute one of the tabs or we would get double audio streams of the meeting, including an echo back from us speaking in the one where we had muted our mic. Now this scenario doesn't work at all. :(

I would not hold your breath on anyone actually considering your provided use cases. Quoted from a similar exchange on a "feature" added 8 years ago: 

"Unfortunately the Chrome devs are tyrannical, fascists, egotists and don't allow anything that they did not think of themselves. The UI/UX team is clearly run by a bunch of people who have absolutely NO UI/UX skills or knowledge, and (as usual) Peter Kasting has already offensively put his foot down about not succumbing to user demand and listening to what user want, and instead telling user what they will get, like it or not."

I tend to agree with this statement and believe he should be removed from the UI teams decision making process immediately. 

#34, that kind of talk will only get this bug closed to new comments. Personal attacks are childish and unhelpful. I suggest you read the Chromium Code of Conduct: https://chromium.googlesource.com/chromium/src/+/master/CODE_OF_CONDUCT.md

That's your opinion. Mine is that is directly constructive to the issue at hand: getting the right person involved to see the error of this change. I'm presenting other opinions that have been echoed in similar situations that reflect the reality of the situation. At this point nothing is being done or even considered about the issue at hand. That is childish and unhelpful in my opinion. 

@34: I'm not in the loop on this decision -- I didn't make the change originally and I'm not the one who would make a different change now.  I commented on this bug in hopes of making the discussion constructive and collecting data that might be useful for anyone who _would_ make a decision on this.  Personally I tend to agree that Mute Tab is more useful than Mute Site.  If you're focusing on me, you're focusing on the wrong target.

@35: Thanks for the helpful (and, indeed, pertinent) reference.

Comment 1 by pkasting@chromium.org, Dec 5
Status: WontFix
"Mute site" means "mute site", not "mute tab".

Working as designed.

Guess we have differing opinions on the definition of constructive and what "collecting data" is. Only after multiple pleas from multiple users was "collecting data" attempted. 

I guess our dictionary discrepancies also apply to pertinence as well. 

Fucking unbelievable.

> Working as designed.

Yeah we know, but it's designed wrong. Stupidly wrong.

The problem is not you don't listen to users, it's you don't listen to common sense.

When this bug has turned into a referendum on someone who has absolutely nothing to do with the change, it's officially off track.  Locking.

I appreciate that this is a frustrating change.  Probably the most constructive way to express that is to post in our feedback forums.  The top issues there are surfaced directly to leadership.

Also, I tested some extensions that provide per-tab muting control and can verify that these two both seem to work and might be useful:

"Mute Tab Shortcuts" provides keyboard shortcuts to mute/unmute and solo/unsolo the current tab:
https://chrome.google.com/webstore/detail/mute-tab-shortcuts/opcjanmpjbdbdpnjfjbboacibokblbhl

"MuteTab" provides one-stop control that lists tabs playing audio and lets you mute them:
https://chrome.google.com/webstore/detail/mutetab/acofndgbcimipbpeoplfjcapdbebbmca

I hope these are helpful for some of the folks who relied on the old behavior here.