Closed Bug 135562 Opened 23 years ago Closed 23 years ago

Should list but greyout other user's folders on the COPY menu item for read privilege folders

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: huang, Assigned: Bienvenu)

References

Details

Attachments

(3 files)

Used 04-04-06-trunk build IMAP Shared: Should list but greyout other user's folders on the COPY menu item for read privilege folders Setup Info: 1) Used two IMAP accounts (Act1 & Act2) 2) Set Read privilege folder in Act1 (for Act2) Steps: 1) Login to Act2. 2) After subscribe that read privilege folder, you should allow to view all the messages in that read privilege folder which setup from Act1 3) Select messages of Act2 Inbox (or other Act2 personal Folders) 4) Actual Results: Select Message|Copy menu|servername|Shared Folder|Users|Act1|..(the readprivilegefolder should list here and greyout, but there are no folders list here at all...) -> will attach a screenshot for this. Expected results: The read privilege folder should be listed and greyout from this COPY menu item.
QA Contact: olgam → huang
Summary: Should list but greyout other user's folders on the COPY menu item for read privilege folders → Should list and greyout other user's read privilege folders on the COPY menu item
Summary: Should list and greyout other user's read privilege folders on the COPY menu item → Should list and greyout other user's read privilege folders on the COPY menu item & context menus
why? If the user can't copy to them, what's the point of putting them in the copy menu? If they were in the copy menu, someone would file a bug that they shouldn't be in the copy menu... I'm pretty sure this is by design, though I didn't write the code.
Summary: Should list and greyout other user's read privilege folders on the COPY menu item & context menus → Should list but greyout other user's folders on the COPY menu item for read privilege folders
This looks like it's the way the menu code is supposed to work. Marking invalid. It doesn't prevent you from filing any messages; it just removes menu items that will never work.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Well. Then how can you explain about the following screen shot that I got for new folder dialog since it did disable/greyout the read privilege folder when I tried to create subfolder from this read privilege folder....can you explain why the code can be implementing on new folder dialog but cannot implementing on COPY menu?
yes, the criteria used for building up the new folder menu list is different than the criteria used for building up the move/copy menu. Think about it this way: whether or not you can create a sub-folder of a folder is different from whether you can move/copy messages into that folder. The code that goes through all the folders figuring out which ones to add to a menu uses a filter function, and filters out folders that don't match the criteria for the menu being created. Does that make sense?
Blocks: 112096
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: