1472317 - relocate tab audio indicator to other side because current position is not touch-friendly

Status: RESOLVED FIXED

(Firefox :: Tabbed Browser, defect, P3)

Description

[Will]

Attachment: touchtabaudioindicator.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180621125625

Steps to reproduce:

Small issue I noticed using Firefox on a Surface tablet: the tab audio indicator is right beside the tab close button, which is way too close for touchscreen use, so if you want to mute that tab by tapping on the tab audio indicator, you can easily tap the tab close button. Edge has it on the other side and this is the better choice not just for touch but probably in general, it also makes more sense visually to have the audio icon beside the tab favicon (I'm sure even people that use mice have accidentally closed tabs when they meant to click the audio indicator)



Expected results:

screenshot attached, Edge on top, Firefox bottom

Comment 1

[Will]

Just thought it's worth adding: I just came across a Chrome developer that said one of the reasons they no longer allow users to mute/unmute via the tab audio icon is because it could result in people accidentally closing the tab because the icon is beside the close tab button, so we really should move it to beside the favicon. It's current location is not only an issue for touchscreen use.

Comment 2

[Will]

Attachment: ptai.png

Another little reason it makes sense to do this: when a pinned tab is playing audio, the icon is overlapping the favicon. It would be more consistent to have the audio icon beside the favicon when it is not pinned. Maybe you could even do a nice little animation of the audio icon shrinking and moving up into the corner when you pin/unpin a tab.

Comment 3

[Will]

This is currently the top voted issue on r/Firefox https://www.reddit.com/r/firefox/comments/k2p52q/is_it_not_more_foolproof_from_clicking_the_close/

(notice another user mentions how this is a real problem on Windows touch devices)

Comment 4

[Will]

This was fixed in Proton, so this can be closed :)