145120 - (Mac only): Main Move/Copy msg menu won't go past 3rd level folders (context, File button will)

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Karen Huang]

Used 05-12-17-7.0 PR1

IMAP Shared UI (Mac 9.x only): Other User can copy messages from context menu, 
but personal menu items for personal folders are not displaying on copy/move 
menu item

1) Setup IMAP Shared Folder for two accounts.
2) From other user's Mail box, tried to copy the the messages from Personal 
Mailbox to other User's Mailbox.

Actual Results: The copy menu item did display with the personal account|Shared 
Folders|User|huang| -- but are not displaying folders from this copy/move menu 
item

Expected results: Copy menu items should fully display for this personal folders 

This is not specific for IMAP Shared Folder.
Laurel mentioned this might be an existing general Window Front end menu item UI 
Mac pp bug.
I am just logging this bug for tracking this problem.
Thanks Gregg for finding this bug.

Comment 1

[laurel]

Mac OS 10.1, too. 
The Message|Move and Message|Copy (main menu items) will not display folders
past the 3rd level folders on any account. However, the context menu Move/Copy
and the File toolbar button will go past that level when cascading the folders menu.

Comment 2

[David :Bienvenu]

so, this has nothing to do with shared folders? If that's correct, can you fix
the summary?

Comment 3

[Michael Buckland]

Discussed in mail news bug meeting.  Decided to minus this bug.

Comment 4

[Olga]

I remove nsbeta1- keyword - it was for MachV.

Comment 5

[Olga]

and added nsbeta1 - for Buffy.

Comment 6

[laurel]

*** Bug 183273 has been marked as a duplicate of this bug. ***

Comment 7

[Samir Gehani]

Mail triage team: nsbeta1-

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420