Closed Bug 39194 Opened 24 years ago Closed 22 years ago

3pane, Should disable "Rename Folder" menu/context menu for IMAP mail fodler & special folders

Categories

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

x86
Windows 98
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
Future

People

(Reporter: huang, Assigned: scottputterman)

Details

(Keywords: polish)

Used 05-12-21-M16 commercial build

Should disable "Rename Fodler" menu/context menu for IMAP mail fodler & special 
folders

1) Login to IMAP Mail Account
2) Select IMAP mail or Special Folders (Inbox,draft,template & trash)
3) Select File| Rename fodlers menu.
4) Actual Results: The rename menu still available for rename these fodlers 
which is not correct.

Expected results: Should disable "Rename Fodler" menu for IMAP mail fodler & 
special folders.
Status: NEW → ASSIGNED
Summary: Should disable "Rename Fodler" menu/context menu for IMAP mail fodler & special folders → 3pane, Should disable "Rename Fodler" menu/context menu for IMAP mail fodler & special folders
Target Milestone: --- → M18
Keywords: nsbeta3, polish
per mail triage:  remove nsbeta3 nomination and move to future milestone.  For
the short term, we will combine items here into three bugs (in 3pane) to address
for nsbetat3:  1. delete, change text, move menuitems;  2. enable/disable and
text changes on context (dynamic);  3.  accelerator keys to work.

When this bug gets revisited after the first release, we'll need to see what
items remaining that need to be addressed.
Keywords: nsbeta3
Summary: 3pane, Should disable "Rename Fodler" menu/context menu for IMAP mail fodler & special folders → 3pane, Should disable "Rename Folder" menu/context menu for IMAP mail fodler & special folders
Target Milestone: M18 → Future
See also bug 67605, "rename" and "delete" should be shown on all folder context 
menus, even if disabled.
Marking wfm, today's trunk build, win2k.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.