message list column divider is always drawn



MailNews: Message Display
15 years ago
13 years ago


(Reporter: Eyal Rozenberg, Unassigned)


Windows 2000

Firefox Tracking Flags

(Not tracked)



(1 attachment)



15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030306
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030306

During a CPU-busy period, I clicked one of the column headers in MailNews, saw
that nothing was happening and switched to another window. Then I switched back,
and noticed that when I moved my mouse over the different column headers, they
appeared pressed (although the mouse wasn't down). When I finally clicked the
mouse, the column divider remained drawn, regardless of what I did (even swith
to other mail folders, or to an account line on the list on the left.

Reproducible: Couldn't Reproduce

Steps to Reproduce:

Screenshot to be added soon.

Comment 1

15 years ago
Created attachment 116642 [details]
screenshot of the gratuitous divider

Comment 2

15 years ago
Problem goes away when closing and re-opening MailNews (without restarting mozilla).

Comment 3

15 years ago
Forgot to mention that the buggy version is the one used to report the bug (i.e.
 2003-03-03 build 6).

Comment 4

14 years ago
Eyal Rozenberg, I've never seen this symptom, but I seldom am running with the 
Classic theme.  If, as I suspect, you no longer see this problem, please mark 
this bug as  Resolved|WorksForMe.

Comment 5

14 years ago
But it's not 'worksforme', it's just very very hard to reproduce. I would ask
that one of the coders have a look over the code for deciding when to draw the
column divider (is this XUL code? I don't know), and if he/she doesn't find any
reason for such a bug to manifest itself, let them mark the bug 'resolved'.
Product: Browser → Seamonkey


13 years ago
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.