Closed Bug 57257 Opened 24 years ago Closed 23 years ago

New folders don't show up in right-click menus and menus

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

Product:
SeaMonkey
Component:
MailNews: Message Display
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: lau, Assigned: ssu0262)

References

Details

Newly created subfolders don't show up in the pop-up menus triggered by
right-clicking a message in the inbox folder.

To reproduce:
1. Under Local Folders, right click on a subfolder (let's refer to it as
subfolder1) that has so many subfolders that requires scrolling when accessed
through pop-up menus, and choose New Subfolder...
2. Type in a new folder name (let's call it newfolder)
3. Select a inbox that has messages in it
4. Right click a message and choose Move To -> Local Folders -> subfolder1 ->
5. The newfolder isn't found under subfolder1 pop-up menu after searching
through the entire scrollable pop-up menu

* The newfolder is accessible using the folder pane on the left and the files
newfolder (size: 0 bytes) and newfolder.msf (size: 1089 bytes) are found in the
filesystem.
** This problem cannot be reproduced when working with subfolders that have only
a few subfolders, which do not require scrolling.

Client: Mozilla/5.0 (X11; U; Linux 2.4.0-test8 i686; en-US; m18) Gecko/20001010
Build ID: 2000101015
The described problem also occurs when trying to access the newfolder from the
Message pull-down menu.

I have to restart Mozilla Mail to see the newfolder appear in the menus.  I also
notice the folder list isn't sorted correctly because the newfolder shows near
the top of the folder list (in the menus, not in the folder pane).  For
instance, if my newfolder has a name beginning with R, Mozilla Mail will place
my newfolder before the folders that begins with A.

Sounds like an RDF problem.
setting bug status to New.  THis may be a dupe though.  It sounds very familiar.
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 63121 has been marked as a duplicate of this bug. ***
QA Contact: esther → sheelar
*** Bug 61028 has been marked as a duplicate of this bug. ***
*** Bug 70937 has been marked as a duplicate of this bug. ***
we have to see if it happens on Mac and then change platforms to ALL ( this bug
is filed for Linux)
*** Bug 72890 has been marked as a duplicate of this bug. ***
Keywords: mostfreq
Summary: New folders don't show up in right-click menus → New folders don't show up in right-click menus and menus
Keywords: mostfreq
*** Bug 82229 has been marked as a duplicate of this bug. ***
As stated in bug# 82229, it appears that first level folders are displaying but 
second level folders are not.
cc naving for filter dialog's New Folder implications.
*** Bug 100301 has been marked as a duplicate of this bug. ***
reassigning to ssu.

Is anyone still seeing this?  I just tried this on the 12/7 Win 2000 build (one
of the dups was Win 98) and it worked for me.
Assignee: putterman → ssu
I am not seeing it on Nightly 2001-12-02-08 (Win32 4.10.2222)  I thought it was
fixed when the ordering of the menus was changed to sort the names.  Actually, I
haven't seen it in a rather long while.

I concur in Works4Me
I also haven't seen this problem since the 0.9.5 release (Mozilla/5.0 (X11; U;
SunOS sun4u; en-US; rv:0.9.5) Gecko/20011017).  The bug also doesn't seem to
come up any more in Linux builds.  It looks like that the bug has been fixed,
probably in earlier builds.
Commercial build: 2001-12-11-06 linux
This problem does not occur anymore. Marking this bug as worksforme.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
verified as worksforme.  Reopen if you happen to see the problem with latest
builds.
Status: RESOLVED → VERIFIED
*** Bug 204215 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Works for me, Mozilla 1.7.5 on WinXP
Reporter: do you still have this problem?
Sorry for my slow response.  I tested on Mozila 1.7.5 on Linux and it now works
for me.

Thank you all for the hardwork.  Mozilla has evolved quite a bit since I filed
the bug.  At last, we can put this bug to bed (at least for now).  :)
You need to log in before you can comment on or make changes to this bug.