Closed Bug 71972 Opened 23 years ago Closed 23 years ago

"View --> Folder Character Coding" should be removed

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 66827

People

(Reporter: jglick, Assigned: sspitzer)

Details

The menu item, "View --> Folder Character Coding" should be removed now that bug 
32714 (Create a UI for Folder Charset)and 65018 (move the folder override ui 
into the folder properties dialog) have been fixed.  The menu item "Edit --> 
Properties (soon to be "Folder Properties")" brings up the exact same dialog. It 
is redundant to have two menu items that open the same dialog.


Part of the discussion from 32714:

------- Additional Comments From Matthew Thomas 2001-01-10 15:54 -------

Why is this in its own dialog, and not part of the Folder Properties window?



------- Additional Comments From timeless@mac.com 2001-01-10 16:21 -------

because when we last discussed it, that window was unimplemented. please reread 
the original nightmarish discussion.



------- Additional Comments From bobj@netscape.com 2001-01-10 16:24 -------

Seconding timeless' comments. That was the original request, but the Folder 
Properties UI was killed. bug 10877 "[FEATURE] UI: Folder property dialogs"
If that feature is revived then as mpt suggests, the Folder Charset belongs
there.


------- Additional Comments From nhotta@netscape.com 2001-01-11 10:05 -------

I think having folder charset UI close to charset menu make it easier to be
discovered by the users who care about charset.We can have folder charset items 
in folder property but we can also keep the current UI.
Nominate as nsbeta1.
Keywords: nsbeta1
This is a duplicate.

*** This bug has been marked as a duplicate of 66827 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
ok, that was really stupid of me...
verified dup.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.