585571 - Reply window goes background on individual mail windows

Status: RESOLVED DUPLICATE of bug 578017

(Thunderbird :: Message Reader UI, defect)

Description

[necokopr]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2

Reply window goes background on individual mail windows

Reproducible: Always

Steps to Reproduce:
1. Double click an email on TB and it pops up in a new window
2. Press 'Reply' or 'Reply All'
3. Reply window glitches and goes to background
Actual Results:  
reply window opened and went to background

Expected Results:  
Reply window opened on top of message window

Comment 1

[Ludovic Hirlimann [:Usul]]

WFM with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:2.0b4pre) Gecko/20100808 Shredder/3.2a1pre.

Can you try in safemode (http://support.mozillamessaging.com/en-US/kb/Safe+Mode) and report your results ?

Comment 2

[Mario Rimann]

(In reply to comment #1)
> Can you try in safemode
> (http://support.mozillamessaging.com/en-US/kb/Safe+Mode) and report your
> results ?

I can confirm the issue on Mac and see that there is a related Bug 578017 for Windows.

Starting Thunderbird in safemode did not change the behaviour. But I'd like to point out that the issue arises after clicking the reply button for the second time, not directly after the start of Thunderbird. Here are my steps to reproduce:

- Start TB
- Double click a message (window opens)
- Click reply (works as expected, compose window comes up on top)
- Close both the compose and the read window
- Double click a message (window opens)
- Click reply
Expected: Compose window pops up on top of the reader window
Actual Result: Compose window pops up *behind* the reader window

BTW: Using Command-R instead of clicking the Reply-Button works fine all the time, also in the "second round" as described above.

Comment 3

[John May]

I can also confirm this bug with 3.1.4 for OS X.  Exactly as described.

Comment 4

[[:Aureliano Buendía]]

Maybe it affects only 3.1.x releases?