Bugzilla

(In reply to Dão Gottwald [:dao] from comment #5)
> (In reply to Sarah Clements [:sclements] from comment #4)

> > And muting/unmuting sound also has the same pattern (you can mute/unmute on hover, by keyboard shortcut or by context menu) so its unclear why having a close button on hover is perceived as problematic. 
> 
> It's more problematic because it's a destructive action, so accidental clicks would be way more annoying.

I hear you, that's a fair concern, which is why the button is positioned slightly over the launcher on the top left. Luckily closing a tab is not truly destructive in a sense of it being gone, but not all users may know how to get it back easily. But I do think product and UX have thought through this.

If we're able to land this early enough in Nightly (and keep it separate from the mute button changes in the event of needing to back it out) we'll be able to get some initial feedback on it before it goes live.

(In reply to Dão Gottwald [:dao] from comment #5)
> (In reply to Sarah Clements [:sclements] from comment #4)

> > And muting/unmuting sound also has the same pattern (you can mute/unmute on hover, by keyboard shortcut or by context menu) so its unclear why having a close button on hover is perceived as problematic. 
> 
> It's more problematic because it's a destructive action, so accidental clicks would be way more annoying.

I hear you, that's a fair concern, which is why the button is positioned slightly over the launcher on the top left. Luckily closing a tab is not truly destructive in a sense of it being gone, but not all users may know how to get it back easily. But I do think product and UX have thought through this.

If we're able to land this early enough in Nightly we'll be able to get some initial feedback on it before it goes live.

(In reply to Dão Gottwald [:dao] from comment #5)
> (In reply to Sarah Clements [:sclements] from comment #4)

> > And muting/unmuting sound also has the same pattern (you can mute/unmute on hover, by keyboard shortcut or by context menu) so its unclear why having a close button on hover is perceived as problematic. 
> 
> It's more problematic because it's a destructive action, so accidental clicks would be way more annoying.

I hear you, that's a fair concern, which is why the button is positioned slightly over the launcher on the top left. Luckily closing a tab is not truly destructive in a sense of it being gone, but not all users may know how to get it back easily. But I do think product and UX have thought through this.

If we're able to land this early enough in Nightly we'll be able to get some initial feedback on it before it goes into release (also for 135 we're still thinking through different roll out scenarios for sidebar/vertical tabs).