3 ms·
> although since extensions don't have access to OS functions, it doesn't tell you if anything is playing a sound or not and that's why this should be a browse
by DeepDuh 14y ago
> although since extensions don't have access to OS functions, it doesn't tell you if anything is playing a sound or not
and that's why this should be a browser feature and not an extension.
- jaredsohn 14y agoAgreed. MuteTab development was started back in Fall 2010 when it wasn't clear to me if Adobe would ever work toward making the changes required to enable such a feature. The extension may live on if there are features that people want but that Google decides do not need to be a part of the browser.