Currently the name of the program folder is "Mozilla" and the shortcut to the program is also called "Mozilla". So currently we have: Mozilla -> Mozilla Mail Profile Manager It should be: Mozilla -> Mozilla Navigator Mozilla Mail Mozilla Profile Manager

Mozilla Mail: I would prefer 'Mozilla Mail & News'. Currently 'Mozilla Mail & News' is used in the Mail/News welcome message. The installer also uses 'Mail & News'. Preferences uses 'Mail and Newsgroups' and 'Mail' only is used in the Tasks menu and as the window title.

It might be an idea to have the Mozilla icons directly in the Program Files menu, and not in a Mozilla submenu. Things like Profile Manager could probably be placed in a folder like 'Mozilla Tools' or 'Mozilla Utilities'. In the Windows 2000 Application Specification Microsoft Windows 2000 UI Fundamentals (attachment http://bugzilla.mozilla.org/showattachment.cgi? attach_id=26342 of bug 69442) it says: "Place your icon to launch your application directly under Start -> Programs. Avoid placing it in a folder under programs. In particular, do not create a folder in the Start Menu in which you only put one item. Often, applications will create a folder based on Company name and then put a single shortcut to launch the application inside that folder. Instead, consider renaming the shortcut to include the company name and dropping the use of the folder. Programs -> My Company à My App (Avoid this) Programs -> My Company My App (Recommended) If you have support applications, tools, or utilities associated with your application, and you wish to publish these in the Start Menu, create a single folder in the Start Menu as a peer of the icon to launch your application and place them there."

over to curt.

Please change Platform/OS to All/All. Also suggest keyword: "mozilla0.9.9" Also suggest to call it *Mozilla Browser* (not Navigator) since this is a more common and recognized term - We "browse". We do not "navigate". Please also add: "Mozilla Composer" and "Mozilla IRC Chat". Please make subject line more clear. Suggestion: "Need New Shortcut Names in Start Button, Quuick Launch Bar, Desktop, etc. (e.g., Mozilla Browser, Mozilla Mail, Mozilla Composer, etc.)"

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

There has been some activity on this bug and its counterpart 123310 recently which has recaptured my attention. I not, however, that this has been nsbeta minused. Should it be targetted for rtm, then? Seems like we want it in the shipping product. The text changes are not problem. I notice in the companion bug that mention was made of using different icons. I'm not in the icon making business (you REALLY don't want me to create art work!) so somebody has to provide those if we want them in. If I get milestone identification and prioritization on this bug I'll do the legwork to get the changes in. (cc'ing syd so he knows what I'm volunteering for.)

> I'm not in the icon making business so somebody has to provide those if we > want them in. I'll take your word for it. Here are the best icons ever made for any application: http://grayrest.com/moz/resources/icons.shtml I'm certain Giovanni and grayrest would be thrilled if these were *finally* implemented. :)

does this apply to Mac? If so, please change `start menu' to `start menu/apple menu' please don't use the `rfe' keyword. some people's convenience is becoming annoyance for those who use bugzilla everyday.

The windows side of this will get fixed in bug 192703

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

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

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

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

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

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

old XPFE installer is dead.