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

Text positioning screwup in index pane (3-pane window)

VERIFIED WORKSFORME

Status

SeaMonkey
MailNews: Message Display
--
major
VERIFIED WORKSFORME
17 years ago
13 years ago

People

(Reporter: Dave Booth, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

Trunk
x86
Windows ME

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; 0.8.1) Gecko/20010313
BuildID:    2001031304

In the message index of the 3-pane view the text fields are spaced so far apart
that I have to scroll one field completely out of view to view the next. They
are no longer aligned to the column headings and sliding the column widths about
doesnt seen to make a difference - If I shrink the subject field down to its
minimum I still cant see the senders name. This is independant of which theme is
applied. This was not a problem in the build 1 week older.

Reproducible: Always
Steps to Reproduce:
Open your mail window :)

Actual Results:  column spacing fouled up as described above. The stretching of
the text fields into the middle distance was so extreme I at first thought all
fields except the subject were completely absent.

Expected Results:  columns should line up with their headings.

Comment 1

17 years ago
This was very recently fixed.
(Reporter)

Comment 2

17 years ago
yep, appears to have been fixed between 3/13 builds and 3/16 builds - probably
in one of the ones I couldnt grab for win32 thanks to the disinfection efforts.

Comment 3

17 years ago
Resolving as WORKSFORME per bugreporters previous comment.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME

Comment 4

17 years ago
Worksforme. This was a one/two day problem. Not happening in apr4 commercial builds.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.