User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:18.104.22.168) Gecko/20101012 Firefox/3.6.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:22.214.171.124) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5 When I right-click on a file in Windows Explorer and select "Send to" and then choose "Mail recipient" Thunderbird 3 opens as well as the new message window with the file that I selected attached. My problem here is not with the main program window opening (see Bug 518444) but with the message window not becoming the active window for the user to edit the message and then send it off. The original explorer window stays active all the time. Reproducible: Always Steps to Reproduce: 1. Right-click on a file in Windows Explorer and select "Send to" and then choose "Mail recipient" 2. Wait for system to respond Actual Results: Windows explorer window remains active and in front of Thunderbird windows. Expected Results: Thunderbird message window with selected attachment active and up front ready for editing by the user so that they can send it off when they are ready to do so.
Can you start thunderbird in -safe-mode (http://support.mozillamessaging.com/en-US/kb/Safe+Mode) ? I'm not seeing this. So it could be another program interfering somehow.
I see the same thing, happens in Safe Mode too - Windows 7 64 bit.
Can you guys check in windows eventvwr if there is anything ?
Component: General → Simple MAPI
Product: Thunderbird → MailNews Core
QA Contact: general → simple-mapi
Version: unspecified → 1.9.2 Branch
There's nothing in the event log. Turns out the window does move to the top of everything, except the explorer window that I'm right clicking on to get the send as menu.
I'm running out of idea on how to figure out what's wrong on your systems
Jave do you still see this?
It's different now. I only see this the first time I try and send mail, second and subsequent times it works as expected. Can reproduce by restarting Thunderbird.
You need to log in before you can comment on or make changes to this bug.