121959 - cut/paste (via Ctrl-X) doesn't paste removed text within msg body

Status: VERIFIED INVALID

(MailNews Core :: Composition, defect)

Description

[Rick Stockton]

If you want to paste the removed text, it must be explicitly copied before
cutting. I have only tried this with plain-text EMails. Instead of the cut text,
I get the previous clipboard contents.

I feel that Ctrl-X should place the text on the clipboard (standard Windows
behavior). I'm not completely sure, but I think that this behavior is a recent
Regression.

Comment 1

[Rick Stockton]

Steps to Reproduce: First, copy a couple of words (from anywhere) onto the
clipboard. Compose a new EMail using plain text. Enter some text in the body of
the message.  Then, cut some portion of this text (Ctrl-X) and try to paste it
back somewhere else in the message body (Ctrl-V).

Actual Results: You don't get your clipped selection; you only get the couple of
words left unchanged frm earlier.

Expected Results: The cut text should replace the old clipboard contents, and be
inserted upon executing the Paste.

Additional Comments: I rate this as 'Normal', but users who don't see the "undo"
menu item might not be able to get their stuff back. I imagine the fix to be
quite easy, since the workaround ('Copy' first, then 'Cut', then 'Paste') is
effective. I think this looks like a bug, not a Development issue (as last
year's 15047, 16513, etc. were).

Comment 2

[Ryan McLoughlin]

Build 2002 01 25 03  Win95, can't reproduce this behavior.  What is your build ID?

Comment 3

[Rick Stockton]

Mozilla/5.0 (Windows; U; Win95; en-US; rv:0.9.7+) Gecko/2002012304
I'm only a couple of days behind you (ryan).

This is interesting:
After consistently seeing this misbehavior in a single session last night, I am
NOT seeing it any more. (The problem doesn't occur in either composing a new
msg, or sending a reply.) Maybe shutting down the computer and restarting
Windows resolved it (Windows Bug?) I have a slightly strange Windows 95 with the
USB updates applied as two patches (actual real OEMs got more changes in their
"2.5" than I have applied).

I would like to recommend changing this bug to status resolved, "INVALID", as
even I am now unable to reproduce the erronious behavior. (I will try to make
this status change as I commit this comment.) 

I agree with 'Close, Can't Reproduce' (or 'One Time Occurrence', or whatever
seems approporiate. Go ahead and clip this in when closing. 

Comment 4

[[e-mail] (gone - use [e-mail] instead)]

verified.