Closed
Bug 351488
Opened 18 years ago
Closed 17 years ago
server/folder location selector sometimes doesn't select
Categories
(Thunderbird :: Mail Window Front End, defect)
Thunderbird
Mail Window Front End
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 385536
People
(Reporter: asa, Assigned: mscott)
References
Details
(Keywords: regression)
I haven't narrowed it down completely yet, but often the selection in the server/folder location selector doesn't work. It gets stalled on one item in the select and will not change until you leave the widget and come back.
Comment 1•18 years ago
|
||
Anything in the Error Console? Could something be happening here where we don't switch to the folder because it's loading (IMAP or a large folder)?
Reporter | ||
Comment 2•18 years ago
|
||
those are both likely possibilities. i speculated when talking with mscott that it was due to some activity on one of my accounts (downloading message headers, junk analysis, etc.) I'll try to watch for it and get a reproducible testcase.
Comment 3•17 years ago
|
||
I have encountered this while running tests on the file location widget, going from local folder back to gmail folder causes it at least 50% of the time.
Comment 6•17 years ago
|
||
reasonably sure this is a regression. tried to find a matching toolkit bug, but not successful so far. bug 362354 is pop, so if it is a correct dup (cause being same) then this bug is not imap only. don't have a testcase.
Keywords: regression
Comment 7•17 years ago
|
||
bug 350839 related?
Comment 8•17 years ago
|
||
Asa, you appear to be the earliest report of this. Do you recall approx what build you were using at the time? Anyone see this in version 1.5? Interesting parallel to bug 319062. However, bug 319062 behavior consistently fails, whereas this bug's behavior is not consistent (but then, we don't have a reproducible testcase either).
Comment 9•17 years ago
|
||
this should be bug 385536 which is fixed on trunk
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•