From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc2) Gecko/20020510 BuildID: 2002051013 Message display should be called only display inline with other names And Return Reciepts, could just be called Recipts, as everyone knows reciepts come back to the user as they do in shops. Reproducible: Always Steps to Reproduce: 1.in preferences->mail & news there are subsections "Message Display" "Composition" "Send Format" "Addressing" "Labels" "Return Reciepts" 3. Actual Results: All could have "Message" at the front of their name, but only the first does. Expected Results: IMO none should have "message" it should just be: _Mail & News "Display" "Composition" "Send Format" "Addressing" "Labels" "Reciepts" Return should be dropped of the last one, as well, i dont think its necessary, as eveyrone knows reciepts are for the user as they are in a shop Seems odd there is no preferences section in bugzilla for mail and news, so i had to file it under a different topic "mail window front end"
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Long names in Message preferences → Shorten mail-news preference catagory names (e.g. Message Display -> Display)
Assignee: mail → nobody
Component: MailNews: Main Mail Window → Preferences
QA Contact: olgam → prefs
Summary: Shorten mail-news preference catagory names (e.g. Message Display -> Display) → Shorten mail-news preference category names (e.g. Message Display -> Display)
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
Status: NEW → UNCONFIRMED
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.