cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jeffg01
Making moves
Status: New idea

v136 introduced dynamically-expanding tab sizes on tabs with audio. This can be laggy though, as a page loads and the video/audio starts playing, causing misclicks. The tabs will also then shrink back down eventually once the audio's been idle for awhile, which can be visually distracting.

There's some kind of thing that can be done with userchrome.css, but this is a workaround that's not viable for most users.

Relevant threads and feedback:

https://connect.mozilla.org/t5/discussions/the-new-tab-mute-button/m-p/89474

https://connect.mozilla.org/t5/discussions/tab-volume-indicator-expanding-tab-space/m-p/90299 

https://www.reddit.com/r/firefox/comments/1j8mdgq/how_can_i_stop_tabs_from_expanding_when/ 

5 Comments
Status changed to: New idea
Jon
Community Manager
Community Manager

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

Agentvirtuel
Collaborator

Hello

According to https://bugzilla.mozilla.org/show_bug.cgi?id=1945993 will be fixed in Firefox 137
Firefox Release Calendar https://whattrainisitnow.com/calendar

jeffg01
Making moves

@AgentvirtuelBy my reading of it, Bug ID 1945993 is something different. That issue looks like it concerns the tabs getting smaller than the specified minimum width. What I'm referring to is the fact that tabs will grow larger when audio starts playing in a tab. This was introduced in v136. Prior to v136, the mute icon appeared over the favicon, and the tab width remained the same size.

Agentvirtuel
Collaborator

Hello

 


@jeffg01 wrote:
Prior to v136, the mute icon appeared over the favicon

Like this by way of illustration
On the left Firefox 136 - Firefox 128 on the right
https://www.youtube.com/embed/vGX8LLf2ul4

doughmean
New member

Yeah, this is driving me nuts. My tabs keeps on shifting left and right, especially when there are multiple tabs getting notifications. There *has* to be a configuration option for this. This also feels like an accessibility nightmare, though I can't personally confirm.