539648 - Selected text of another / wrong message quoted after selecting text in message A, then right-click on message B > Reply

Status: VERIFIED DUPLICATE of bug 507541

(Thunderbird :: Mail Window Front End, defect)

Description

[JWJ van der Drift]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; nl; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; nl; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b2pre Thunderbird/3.0

When selecting text in message A and replying to message B, the selected text from message A is pasted into the reply on message B.

This only occurs when replying to to message B from the inbox.
It does not occur when message B is opened in a tab.

Reproducible: Always

Steps to Reproduce:
1. Open message A and select text
2. Close message A
3. Reply to message B from the inbox (do not open message B)
Actual Results:  
The selected text from message A are pasted into the reply

Expected Results:  
The reply should contain the complete text of the message replying to.

Comment 1

[Ludovic Hirlimann [:Usul]]

This WFM on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1.

Can you try with launching thunderbird in -safe-mode (http://kb.mozillazine.org/Safe_mode) ?

If it still happens in -safe-mode, please details your reproduction steps a bit more  (Where does A opens ? Hwo do youd do the reply without opening etc ...)

Comment 2

[JWJ van der Drift]

Yes, this also happens in safemode
Hereby my steps

Open message A from the inbox in a tab
Select text in message A
Close (the tab of) message A (keep the text selected!)
Reply to message B WITHOUT opening message B by rightclicking on message B

The reply will show the selected text from message A

I will add some screenshots

Comment 3

[JWJ van der Drift]

Attachment: Screenshot #1

Comment 4

[JWJ van der Drift]

Attachment: Screenshot #2

Comment 5

[JWJ van der Drift]

Attachment: Screenshot #3

Comment 6

[JWJ van der Drift]

Attachment: Screenshot #4

Comment 7

[Ludovic Hirlimann [:Usul]]

Ok how do your sort your mailbox,  you use sort it by date and theh Group By G , right ?

Comment 8

[JWJ van der Drift]

That is correct, date descending.

In reaction to your question, I have tested it in safemode with the inbox sorted on subject (ascending), not grouped. This has the same result

Comment 9

[Ludovic Hirlimann [:Usul]]

Aureliano can you test on XP/Win7 ?

Comment 10

[[:Aureliano Buendía]]

I can confirm here

Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100113 Lightning/1.0b1 Shredder/3.0.2pre ID:20100113033347

but for reproduce the described behaviour is *necessary* that preview pane is off.
When I repeat the steps in comment #0, with previw pane displayed I can't reproduce the behaviour... could be a regression related to fixes of bug #521026?

Comment 11

[JWJ van der Drift]

I disagree. With preview pane on, I can reproduce this bug.

It is *necessary* not to preview message B first

Comment 12

[Ludovic Hirlimann [:Usul]]

(In reply to comment #10)

> When I repeat the steps in comment #0, with previw pane displayed I can't
> reproduce the behaviour... could be a regression related to fixes of bug
> #521026?

Can we do a regression finding  and if the date matches than it's probably one.

Comment 13

[[:Aureliano Buendía]]

(In reply to comment #11)
> I disagree. With preview pane on, I can reproduce this bug.
> 
> It is *necessary* not to preview message B first
I think this because in your release (3.0.0) bug #521026 was don't fixed. I make test with next 3.0.1pre.

Comment 14

[JWJ van der Drift]

Hi,
I can reproduce this issue, following the steps in comment #0, in version 3.0.1

Mozilla/5.0 (Windows; U; Windows NT 6.1; nl; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1

Comment 15

[JWJ van der Drift]

Hi,
this seems to be solved in 3.0.3

Comment 16

[JWJ van der Drift]

(In reply to comment #15)
> Hi,
> this seems to be solved in 3.0.3

No, it's not....

Comment 17

[Thomas D. (:thomas8)]

TB17, winXP, I cannot reproduce JWJ's exact scenario of comment 0 using these steps:

1. Open message A in a tab and select text
2. Close message A (without deselecting text)
3. From inbox, *right-click* on msg B, pick "Reply" from context menu

Actual Results
(per my test)
full text of msg B correctly quoted
(per comment 0, but I can't reproduce)
The selected text from message A is wrongly pasted into the reply (instead of full text from msg B)

JWJ van der Drift (reporter), can you still reproduce exactly your old steps (involving tabs)?
If yes, can you provide more detailed steps?

However, it's simple to reproduce this bug in a slight variation, with much simpler STR:

1) select some text in 3 pane's msg preview of msg A
2) *right-click* on Msg B, then "Reply" from context menu

Actual result:
- selected text of Msg A wrongly quoted in reply to Msg B (and confusing mess because we actually keep the right subject of Msg B, only the quoted text is wrongly taken from Msg A).

Expected result:
- quote full text of Msg B

Morphing summary accordingly.

Comment 18

[Thomas D. (:thomas8)]

For ease and speed of workflow, resolving this as duplicate of remaining problem, bug 507541 with better description.

JWJ, pls do comment here if you still see *your* issue with *your* original steps involving tabs.
If yes, we could consider
- reopening this bug
- or adding a comment in bug 507541 to cover this variant

Comment 19

[JWJ van der Drift]

Using TB 17.0.8, I can NOT reproduce the steps from  https://bugzilla.mozilla.org/show_bug.cgi?id=539648#c0.

I can confirm that bug https://bugzilla.mozilla.org/show_bug.cgi?id=507541 still is actual

Comment 20

[Thomas D. (:thomas8)]

(In reply to JWJ van der Drift from comment #19)
> Using TB 17.0.8, I can NOT reproduce the steps from 
> https://bugzilla.mozilla.org/show_bug.cgi?id=539648#c0.
> 
> I can confirm that bug https://bugzilla.mozilla.org/show_bug.cgi?id=507541
> still is actual

JWJ, thanks for quick response, that's helpful and appreciated :)
So reporter's comment 19 verifies my analysis of comment 17 and comment 18 which resolved this duplicate of bug 507541.