Closed Bug 623769 Opened 14 years ago Closed 14 years ago

Message opens in new window even if "an existing message window" is selected

Categories

(Thunderbird :: Message Reader UI, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: justridingalong, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 GTB7.1 ( .NET CLR 3.5.30729; .NET4.0C) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 Sometimes, clicking on a message will open the message in a new window, even though the "existing message window" option is selected. It usually happens immediately after launching Thunderbird. Reproducible: Sometimes Steps to Reproduce: 1. Launch Thunderbird 2. Tools > Options > Reading & Display 3. Open messages in > an existing message window 4. Click OK 5. Quit/exit Thunderbird 6. Re-launch Thunderbird 7. Click on a message in the list of messages 8. Click on the next message in that list Actual Results: Instead of opening the message in the existing window, the message will sometimes load in a new window or a new tab (despite having selected "an existing window" in the preferences). Expected Results: Expected to have the message load/open in the existing window. This only started happening recently. I use Thunderbird to access two IMAP accounts and my gmail account, and the problem will occur intermittently with all three accounts. It seems to happen right after launching Thunderbird.
No, it doesn't seem to happen in safe-mode.
(In reply to comment #2) > No, it doesn't seem to happen in safe-mode. So your issues lies in an extension or a theme. Try disabling them all and reanabling them one by one, until you find the culprit. Once you know which add-on produces the issue let the add-on author know. This is a non Thunderbird bug -> INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.