Closed
Bug 10426
Opened 25 years ago
Closed 25 years ago
Thread pane scrollbar column position problem when maximized
Categories
(MailNews Core :: Backend, defect, P3)
MailNews Core
Backend
Tracking
(Not tracked)
VERIFIED
FIXED
M10
People
(Reporter: laurel, Assigned: hyatt)
References
Details
(Whiteboard: [PR1])
Using jul22 builds on linux rh5.2, NT 4.0 and Mac OS 8.51 The scrollbar can end up in the middle of the thread pane if you've scrolled to the bottom of the message list in a restored window state then maximize the Messenger window. 1. Open Messenger window. Select a mail folder (or newgroup) with many messages in it for easier scrollbar appearance. 2. Resize the window to half screen size or smaller. 3. Take the scrollbar slider and move it to the bottom, so you're placed at the end of the thread pane message list. Scrollbar is at the far right column of the restored window. 4. Maximize the messenger window. Result: The scrollbar does not move to the far right column position, rather it stays in the same place as it was when the window was in restored state. To rid the maximized window of this you must change to another folder and back, switching between maximized and restored state doesn't take care of it.
Assignee | ||
Comment 3•25 years ago
|
||
Moving to M10.
Sounds like this needs to be fixed for PR1, so I added a note to the Status Whiteboard
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•25 years ago
|
||
Fixed.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•25 years ago
|
||
Build 1999090208M10: Win32/NT4, Build 1999090108M10: Linux/Redhat 6.0 Build 1999090208M10: Mac 8.5.1 Verified Fixed. Once the scrollbar appears in the thread pane I scrolled to the last message, selected the maximize button and the scrollbar appears in the expected position, the far right column.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•