Closed
Bug 196961
Opened 23 years ago
Closed 23 years ago
Move cursor and Junk, Read and Flag columns shake
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: nbaca, Assigned: sspitzer)
Details
(Keywords: qawanted)
Trunk build 2003-03-11: WinXP
Trunk build 2003-03-10: WinMe
Overview: In a new profile using the Classic skin - in the thread pane move the
cursor over the thread pane borders (top, right, lower and left) and notice the
Junk, Read and Flag columns shake.
Steps to reproduce:
1. Create a new profile and add an account
2. Retreive messages and move the cursor from the thread pane down to the
message pane.
3. Move the cursor from the thread pane to the right so the pointer is in the
scrollbar area.
4. Move the cursor from the thread pane to the top where the column headers reside.
5. Move the cursor from the thread pane to the left so it touches the divider
Actual Results: In steps 2, 3, 4 and 5 you may see some columns shake. The ones
that shake appear to be columns which cannot be sized (i.e. Junk, Flag and Read
column which procudes the green diamond).
Try removing one of these columns and try again. You'll see that other columns
may not shake anymore.
It did not occur:
- With existing profiles
- New profiles using the Modern skin
| Reporter | ||
Comment 1•23 years ago
|
||
Marking nsbeta1.
I don't see this problem:
- Windows using the Modern skin
- Mac using Classic skin
Keywords: nsbeta1
QA Contact: esther → nbaca
Comment 2•23 years ago
|
||
Mail triage team: need info. Ninoschka to work with Esther to reproduce this.
Keywords: qawanted
Whiteboard: [need info]
Comment 3•23 years ago
|
||
Mail triage team: nsbeta1-. QA cannot reproduce this.
| Reporter | ||
Comment 4•23 years ago
|
||
Trunk build 2003-03-13: WinXP, WinMe using the classic skin.
Marking Worksforme.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•