If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Tab close buttons disappear from all tabs but current when browser.tabs.closeButtons=1

RESOLVED DUPLICATE of bug 491291

Status

()

Firefox
Tabbed Browser
RESOLVED DUPLICATE of bug 491291
7 years ago
7 years ago

People

(Reporter: Alex Riesen, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0b11) Gecko/20110210 Firefox/4.0b11
Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b11) Gecko/20110210 Firefox/4.0b11

The close button on the current tab is always displayed, it is the close buttons on the other tabs which disappear and reappear at their own will.
Sometimes I can bring them back by opening a new tab and immediately closing it. Sometimes not.

Reproducible: Sometimes

Steps to Reproduce:
1. Set the option to have the close button on every tab
2. Have many tabs
3. Keep an eye on the close buttons of inactive tabs while doing your browsing
Actual Results:  
Sometimes the close buttons on inactive tabs disappear

Expected Results:  
They shouldn't

Comment 1

7 years ago
Mozilla/5.0 (X11; Linux i686; rv:2.0b12pre) Gecko/20110221 Firefox/4.0b12pre

Setting bug to New, considering what is written here:

http://kb.mozillazine.org/Browser.tabs.closeButtons

Although, I am not sure if this setting isn't overwritten when more than 9 tabs are opened.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I believe this is intended when we display the scroll arrows and too many tabs are open.
(Reporter)

Comment 3

7 years ago
A way to override this would be nice. Because that's exactly when I have many tabs I miss the close buttons most.

Updated

7 years ago
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 491291
Status: RESOLVED → VERIFIED
(Reporter)

Comment 5

7 years ago
Please, don't just close. Ok, it may be not a bug (since the annoying behavior seem to be documented). But it would be a nice enhancement to be able to override the behavior (10 tabs! Where on the earth have you this number?!)

I cannot reopen the bug this one is duplicate of, but if I don't, I'm sure the issue will be just ignored for ever.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
You can override the behavior by modifying the browser.tabs.tabClipWidth preference.
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago7 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 491291
(Reporter)

Comment 7

7 years ago
No, I can't. The default value is 140 (yet another senseless constant?), and no matter to what I set it (1, or 200), the close buttons disappear.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Don't reopen this bug again. The preference isn't live. If you have further questions, please ask them in the appropriate forum.
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago7 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 491291
(Reporter)

Comment 9

7 years ago
Ok, for people who don't belong to mozilla elite: "preference isn't live" should mean "restart the browser after changing".

Besides, the (senseless) value of preference browser.tabs.tabClipWidth means minimal width the first non-pinned tab can have before tab bar starts loosing close buttons. If the "first non-pinned tab" gets any narrower, the close buttons disappear.

Setting the preference to 0 restores the close buttons according to closeButtons setting.

For the interested, try looking through this: browser/base/content/tabbrowser.xml, search for "adjustTabstrip".

So yes, I agree, that reopening bug is not needed. I also note for myself and anyone who cares to read this comment this far that this particular mozilla developer was an unpleasant source of information in somewhat open-ended form.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---

Updated

7 years ago
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago7 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 491291
You need to log in before you can comment on or make changes to this bug.