Closed
Bug 101775
Opened 24 years ago
Closed 24 years ago
Column reordering doesnt work correctly in Mail/News
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: scttran, Assigned: hewitt)
Details
Attachments
(1 file)
|
2.15 KB,
patch
|
Details | Diff | Splinter Review |
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
BuildID: 2001092603
New column reordering doesnt place mail/news columns where they should be.
Reproducible: Always
Steps to Reproduce:
1. Open up Mozilla Mail/News
2. Start dragging the columns for Mail/News around. (Subject, Sender etc...)
3. Observe that the columns are not placed where they should be
Actual Results: Columns are not placed where they should be.
Expected Results: Columns should be placed in expected position.
There's probably an older bug about this. We don't support reordering columns
at this time.
QA Contact: esther → olgam
| Assignee | ||
Comment 2•24 years ago
|
||
laurel, column ordering is a new feature that I checked in last night. In fact,
this is a bug that causes it to behave erratically.
Status: NEW → ASSIGNED
| Assignee | ||
Comment 3•24 years ago
|
||
Comment 5•24 years ago
|
||
sr=hyatt
Comment 6•24 years ago
|
||
I'm sure you cover this in your patch, but I want to make sure - the column
picker box(far right) winds up getting moved to the middle of the column set
after you do your first re-ordering operation, and there's no way to get it
back. You fixed that part too right? :-)
| Assignee | ||
Comment 7•24 years ago
|
||
Yes, that is specifically what this patch fixes.
Comment 8•24 years ago
|
||
r=blake
Comment 9•24 years ago
|
||
Is this fix on the trunk or the branch?
| Assignee | ||
Comment 10•24 years ago
|
||
fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 11•24 years ago
|
||
Verified on trunk build 2001-10-25 - Win 2K, Linux, Mac 9.1.
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•