Closed Bug 314737 Opened 20 years ago Closed 20 years ago

missing scroll UI for attachment list

Categories

(Thunderbird :: General, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 223340

People

(Reporter: andrixnet, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Displaying a message with attached files shows the list of attachements at the bottom of the window. If there are many files attached, the size of this area increases proportionally, but no scroll appears. I have encountered messages with many attachements (like 20 or so) where on 800x600 I barely had a few lines visible from the message text. Reproducible: Always Steps to Reproduce: 1.have a message with many attachements 2.open it in the default window configuration (folders on left, message list on top-right, message text on bottom-right) 3. Actual Results: If many attachements, attachement list can occupy a major portion of the window, leaving very little space for reading the message Expected Results: attachement list should show at most 2 lines and scroll controls if more.
Summary: missing scroll UI for attachements list → missing scroll UI for attachment list
I have filmed a short clip showing the multiple resizing operations that happen when I display a message. Most evident while opening spam, postmaster errors, message forwarded multiple times, etc ftp://znets.dyn.ro/pub/tests/test-thunderbird.mpg [4MB] recorded @ 320x240x30fps.
Per email from reporter, these have been tested on 1.5 and still appear.
Version: unspecified → 1.5
Duplicate of bug 223340 (and/or bug 282068)?
Whiteboard: DUPEME
*** This bug has been marked as a duplicate of 223340 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Cleanup *dupeme* whiteboard flag from bugs that are marked as Resolved Duplicate!
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.