226151 - new folder doesn't show up in the folder list pane

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Bob Lockie]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031110
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031110

Creating new folder when creating a new filter does not show the folder name in
the folder list pane until Mozilla/Mail is restarted.

Reproducible: Always

Steps to Reproduce:
1. Right click on a message and select "Create Filter From Message".
2. Click on "New Folder".
3. Select any folder as the parent and enter any folder name.
4. Press return or select the "OK" button and the folder is created but doesn't
show up in the folder list until Mozilla/Mail is restarted.
Actual Results:  
The folder name was not visible.

Expected Results:  
The folder name should have immediately appeared in the folder list pane.

Comment 1

[Charles Fenwick]

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

Comment 2

[Charles Fenwick]

Unduping.
After mucking around with this new folder business for awhile, I noticed that
there are still issues with existing subfolders.  That is, if the new folder is
directly under Inbox, then this works.  However, if the new folder is a
subfolder of a folder under Inbox, then this problem occurs.

Comment 3

[Charles Fenwick]

Confirming.

To reproduce this bug one does not need to have to go through the create filter
dialog.  Just right click on an existing Inbox folder and select 'New
Subfolder'.   Type in a file name and hit enter.  It appears that nothing has
happened, but if you hit enter again, you get the "A folder with that name
already exists message"
If you close Mozilla and re-open, you will see that the (sub)folder was indeed
created.

This looks to be the same issue as bug 2255235 (I get the same "line 0: uncaught
exception: [Exception... "Component returned failure code: 0x80550013
[nsIRDFCompositeDataSource.DoCommand]" JS error mentioned in that bug), with the
difference being that this is for a subfolder.

Fixing this bug would fix bug 226150 as well.

Comment 4

[David :Bienvenu]

Charles, have you tried a build from 11/11? I believe this is all fixed.

Comment 5

[Charles Fenwick]

David,

Apologies for not stating as such, but the problems I see with subfolders are
occurring on a current trunk build.

The problem with folders was indeed fixed, it's just that it looks like a
problem still exists with subfolders

Comment 6

[Sven Krohlas]

This seems to work for me using 2003121014 on Linux.
Could anyone verify this?

Comment 7

[Asa Dotzler [:asa]]

related to bug 225372 or bug 225371? Are all of these can't write bugs fixed in
the latest nightly builds? 

Bienvenu, is there a fixed bug these should be duped against?

Comment 8

[David :Bienvenu]

I thought this was a dup of bug 225235 - bug 224849 is also related.

Comment 9

[Charles Fenwick]

When I first came across this bug and did a little bit of testing I thought it
to be a dupe of bug 225235 (,which through testing, I observed to be fixed).

However, after playing around for a little bit I saw a problem.

I could create a subfolder of the Inbox 'Foo' just fine.  However, if I tried to
make a subfolder of 'Foo' (calling it 'Bar'), then the folder would not be
created (I would get the same error as in bug 225235).  (Comment 3 details my
observations at the time .)

I tried again tonight.  I created a subfolder of Inbox 'Spam' just fine.  I
closed out and created a subfolder of 'Spam' (called 'Eggs') just fine. 
However, when I tried to create a subfolder of 'Foo' (called 'Gaz') I
encountered the problem previously reported.

This is probably related to bug 225371 in that I was able to delete 'Spam' and
its subfolder.  I am not, however, able to delete 'Foo' or its subfolders.

(All of this testing ocurred on CVS builds that were/are current.)

Comment 10

[David :Bienvenu]

I'll try it out.

Comment 11

[David :Bienvenu]

I'm not able to reproduce this. I tried before the first time you said you were
still having the problem and couldn't reproduce it then, either. I'm not sure
what's going on here...

Comment 12

[Asa Dotzler [:asa]]

not going to hold 1.6 for a problem that we can't reproduce.

Comment 13

[Sven Krohlas]

Does anyone still see this? Or may I mark this WFM?

Comment 14

[Charles Fenwick]

Bug Day 

Yeah, this WorksForMe now as well... since I confirmed it, I'll mark it as such...