Closed Bug 185940 Opened 17 years ago Closed 11 years ago

"Move" on "Message" menu should be "Move To" to match context menu

Categories

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

defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED FIXED
seamonkey2.0a2

People

(Reporter: bugzilla, Assigned: mkmelin)

Details

Attachments

(1 file, 1 obsolete file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021204
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021204

In the context menu there are items labelled 'Move To' and 'Copy To', while on
the main 'Messages' menu at the top they are labelled 'Move' and 'Copy'.

Reproducible: Always

Steps to Reproduce:
Attached patch Patch to solve this 'bug' (obsolete) — Splinter Review
I patched this against mozilla-1.2.1 code.
QA Contact: olgam → laurel
Adding jglick for UI feedback.  This sort of thing is typically governed by a 
published specification.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
REOPEN, this seems like a reasonable change.
I don't see any reason why they should be different. I don't know
whether "Move" or "Move To" is the right choice though.
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: mail → nobody
QA Contact: laurel → message-display
Making it "Move to" and "Copy to" sounds like an improvement to me.
Seems like it could be a change for the better.
Attached patch proposed fixSplinter Review
Patch to change it to "Copy To" and "Move To". 
I'm unsure if the To should be capitalized in this context, but it does look better IMO.
Assignee: nobody → mkmelin+mozilla
Attachment #109617 - Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #343252 - Flags: ui-review?(clarkbw)
Attachment #343252 - Flags: review?(philringnalda)
Attachment #343252 - Flags: superreview?(neil)
Comment on attachment 343252 [details] [diff] [review]
proposed fix

The capital "To" looks good.  It will also be consistent with the context menus.
Attachment #343252 - Flags: ui-review?(clarkbw) → ui-review+
Comment on attachment 343252 [details] [diff] [review]
proposed fix

I hate this new entity renaming all the time :-(
Attachment #343252 - Flags: superreview?(neil) → superreview+
Attachment #343252 - Flags: review?(philringnalda) → review+
changeset:   634:d8cbe485c967
http://hg.mozilla.org/comm-central/rev/d8cbe485c967

->FIXED (both thunderbird and seamonkey)
Status: ASSIGNED → RESOLVED
Closed: 14 years ago11 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.0a2
You need to log in before you can comment on or make changes to this bug.