New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 763978 link

Starred by 3 users

Issue metadata

Status: Duplicate
Owner:
Last visit > 30 days ago
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

Improved tab mute behavior

Project Member Reported by col...@chromium.org, Sep 11 2017

Issue description

Feature description:

Currently tabs do not mute by default. Users need to use a secondary menu to selectively mute tabs. Additionally, the mute state of a tab is displayed in a small icon which is difficult to see.

I propose a new behavior that will give users more transparency about the mute/unmute. UX for this should be similar to the pop-up blocker. Users will be able to set a default behavior for mute state. They can then choose how to handle mute for each site as they can for pop-ups today. They should also be able to temporarily allow audio on a site.

Eng owner: colish
Product owner: 

Design doc: Still todo

Are you planning on experimenting before launch? yes
Any new strings? TBD
Any implications for Google webservices (i.e. sync, translate)? unsure
Binary size? Unsure
Do the existing perf tests exercise all aspects of your new feature(s)? Unsure

 
Cc: mlamouri@chromium.org
Mounir, this seems related to, for example, https://github.com/WICG/interventions/issues/28, but that's only for iframes. Do you know who Dan should talk to about reducing the intrusiveness of top-level audio?

Comment 2 by m...@chromium.org, Nov 15 2017

Cc: steimel@chromium.org
Mergedinto: 774747
Status: Duplicate (was: Assigned)
I believe site muting should address this :)

Sign in to add a comment