'Clickable tab mute was used by a tiny sliver of the userbase, in part because it was never a shipped feature.
The functionality of muting an individual tab still remains accessible to extensions, which can mute tabs on-demand or automatically in response to heuristics the intent is that extension developers provide options here beyond what are built in' Contributing factors include potential dataloss risk, code complexity, behavioral complexity, and confusing interactions with mute-whole-site capabilities that the general userbase finds more compelling. 'The official reason is a combination of a large number of factors, but primarily that this is a symptom band-aid that doesn't address the underlying problems that lead to people wanting to mute tabs, and we should be spending our time addressing those problems. Things have changed as of v71, inexplicably:Peter Kasting explained in Reddit the reasons for this:
