Closed Bug 536839 Opened 15 years ago Closed 15 years ago

Account manager settings not visible on small screens, no scroll bar

Categories

(Thunderbird :: Account Manager, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 416263

People

(Reporter: dasy2k1, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.43 Safari/532.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b2pre Thunderbird/3.0 when trying to set my accounts up on a netbook with a small (10.1") screen some of the options in the account manager are not visible due to the small size of the widow. especially the sub menus with lots in them (like the Engimal addon GPG options) given my window manager will not let me make the window longer than the height of the screen (even if i drag it off the top then try to stretch) i cant get to these menus at all, a simple scroll bar in the acout manager window that was active if the window was smaller than the content would solve this problem totally Reproducible: Always Steps to Reproduce: 1.use thunderbird on a netbook with a small screen (or set your resolution to something tiny like 640x480) 2.from edit => account settings open one of the submenus such as copies and folders 3.try to set somthing other than default in the settings at the bottom of the list Actual Results: impossible to get to the settings Expected Results: scroll bar on right of settings window allows you to scroll down untill the settings you want are visible netbooks are becoming more and more popular, why should i need a 21" screen to use thunderbird?
Whiteboard: dupme
I verify this bug. It is impossible to change your account settings on a netbook. The account settings window needs a scrollbar.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Cleanup *dupeme* whiteboard flag from bugs that are marked as Resolved Duplicate!
Whiteboard: dupme
You need to log in before you can comment on or make changes to this bug.