customize status bar broken

RESOLVED INVALID

Status

Thunderbird
Toolbars and Tabs
RESOLVED INVALID
5 years ago
5 years ago

People

(Reporter: david, Unassigned)

Tracking

25 Branch
x86_64
Windows 7

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
I cannot customize the status bar.  It's like the status bar is locked regarding customization.  I can't add icons nor remove the one that remains: I have two zoom buttons there (i.e. +/-).  They function normally, but can not be removed.  Placing a cursor over them in the customize mode results in no change of the cursor, which normally changes to indicate a move is possible (this still functions as expected in the Toolbar customize).  When testing an icon from the customize popup, moving it over the status bar results in the invalid drop location cursor.

Also, a right mouse click over the status bar results in nothing, where normally that would net a context popup for customizing.

I tested it with two different profiles.  I also tested it via a "restart with addons disabled"=safe mode.

The status bar can be made to hide/unhide via View> Toolbars> tick/untick.

additional consideration:
One addon I have will add and remove it's status bar icon via it's Options menu, that being the addon: Version In Add-on Bar.
One addon will no longer add/display it's icon, that one being: SlideShow.
The online/offline button works normally.  The status bar Unread and Total indicators display normally.

Thanks for your consideration.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Neither Thunderbird 17.0.8 nor the Thunderbird Daily versions support customizing the status bar. I don't have the zoom buttons in the status bar, these can also likely be provided by an add-on. If an add-on provides buttons for the status bar and you don't want them, please check if you can turn the off in the add-on's settings and contact the developer if it isn't possible.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.