On 9/23/2014 6:03 PM, Paul B. Gallagher wrote:
Ray_Net wrote:
Paul B. Gallagher wrote, On 22/09/2014 22:58:
hawker wrote:
On 9/22/2014 3:45 PM, Paul B. Gallagher wrote:
hawker wrote:
Just noticed a new issue in mail 2.26.1 that was not there before I
updated. Perhaps it has been fixed in 2.29.
I often do a "replay" to an email just so I can get the formatting
of a
message and written by. I then copy and past that into some other
e-mail
I am responding to. This happens when I am responding to two
e-mails at
once that must go to the same folks.
What exactly is a "replay"? Give step-by-step instructions so someone
else can try it.
Or do you mean "rePLY"? If so, it works fine for me in 2.26.1,
regardless of whether the source or target or both are HTML or plain
text.
Up to now that has worked fine. It 2.26.1 I can copy and past[e] the
message body or the "On mm/dd/yy HH:MM am SoandSo Wrote:" but if I
try
to select both it won't past[e] (just blank) into the new message.
Any idea what is causing this, how to fix or if it is a known bug?
Nope.
Yes, darn typos. I did intend to say "Reply" not sure how that
happened.
Anyway odd. Are you sure you did what I said? Let me be more clear.
1) Reply to two different messages.
2) Select the "On mm/dd/yy HH:MM am SoandSo Wrote:" and the message
body
below.
3) Hit CTRL-C (Windows machine) or CTRL-X.
4) Go to the other e-mail and hit CTRL-P to past it. I get nothing.
If I only select the "On mm/dd/yy HH:MM am SoandSo Wrote:" or the
message body but not both it works as expected.
Yes, I can easily PASTE either or both into a new message.
Win7 Pro SP1, SM 2.26.1.
Do us a favor and disable that autocorrupt feature that keeps
substituting "past" for "paste."
Have you read my reply explaining in détails how to reproduce easely
this bug ?
Sure. Unable to reproduce, as I said earlier. Copy works fine, paste
works fine, even print (Ctrl-P) works fine.
This "bug" is interesting.
Ray - If I try your steps it works fine, however with my steps it does
not work. Furthermore this bug just started at 2.26.1 and did not with
whatever I was using before (probably 2.24 or around there). It sounds
like your bug goes back further.
So somehow this breaks for some users under some conditions only.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
