270653 - Accounts tree collapsed when opening Mail&News

Status: VERIFIED DUPLICATE of bug 272602

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Troodon]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041118
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041118

 

Reproducible: Always
Steps to Reproduce:
1. Open Mail&News and make sure you have some accounts expanded.
2. Exit completly Mozilla (close all components).
3. Open Mozilla Browser and from inside it open Mail&News.
4. See all the accounts are collapsed (tree satus not remembered).
5. Close Mail&News and open it again within the broser.
6. Now the tree's satus is remembered.


Expected Results:  
Tree's status should be remembered.

If Mail&News is opened directly, all works as expected.

Similar, but now equal to bug 123029.

Comment 1

[Troodon]

With Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041124
this changed a bit.
Now it only happens when the last closed window (when closing "the whole" Suite)
is a browser one and after that the first opened is a Mail&News one (direct
opening Mail&News).

Comment 2

[hansen]

Well you're not crazy, but have you checked the latest nightly, cause at least
Thunderbird got it fixed two nights ago and I'm sure it was a core thing, so it
should be present in Mozilla too.

Comment 3

[Troodon]

It doesn't seems to happen with Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.8a6) Gecko/20041204. What is the bug you're referring to? I have only found
bug 272829 and bug 272602 and neither of them appears as fixed.

Comment 4

[Jan Kosnar]

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a5) Gecko/20041122
I see a little bit different behavior on this, for me it seem to be like opening
Mail from different location (from inside of a suite / from quick launch) always
destructs the state of acounts set from the other location.

Comment 5

[Troodon]

(In reply to comment #4)
> Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a5) Gecko/20041122
> I see a little bit different behavior on this, for me it seem to be like opening
> Mail from different location (from inside of a suite / from quick launch) always
> destructs the state of acounts set from the other location.
> 
> 

Could you try a newer build to see if it's also fixed for you?

Comment 6

[Peter Lairo]

In all fairness (although I disagree with that decision), you might want to look
at the reasons for bug 103010.

The justification for this bug is the comment: bug 103010 comment #16.

PS. You might want to add "news" to the summary. I also think the bug's
"product" may be wrong.

Comment 7

[Troodon]

(In reply to comment #6)
> In all fairness (although I disagree with that decision), you might want to look
> at the reasons for bug 103010.
> 
> The justification for this bug is the comment: bug 103010 comment #16.
> 
> PS. You might want to add "news" to the summary. I also think the bug's
> "product" may be wrong.

This bug is ONLY about POP accounts (I don't have any news account). What
product do you suggest? This is for Mail&News and for Thunderbird there is bug
272829.
Also, this bug appeared recently and bug 103010 and its fix are three years old.

Comment 8

[Peter Lairo]

(In reply to comment #7)
> This bug is ONLY about POP accounts 

Sorry. Then the summary should state that. (I have IMAP & newsgroups)

> What product do you suggest? 
> This is for Mail&News and for Thunderbird there is bug 272829.

I thought this might be a "core" issue. (this MailNews-TB split is confusing)

> this bug appeared recently, and bug 103010 and its fix are three years old.

Duplicates do happen, and this appeared to be one. Solution: Fix Summary.

Comment 9

[David :Bienvenu]

this is a core problem, and it has been fixed - the original bug, against which
this is dup'ed, is still open for other issues, but the basic problem has been
fixed)

*** This bug has been marked as a duplicate of 272602 ***

Comment 10

[Troodon]

In reply to comment 8 and comment 9:
I didn't marked this bug as dupe because I dind't know what bug was referring to
comment 2 (see comment 3 and bug 272602, comment 22). Anyway, thank you very
much for marking it as dupe of the right bug :-).