Opening email in new window replaces exisiting open window. Settings, prefs.js not being correctly saved.
Categories
(Thunderbird :: Preferences, defect)
Tracking
(Not tracked)
People
(Reporter: zaga1, Unassigned)
Details
(Keywords: dupeme)
Attachments
(1 obsolete file)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:120.0) Gecko/20100101 Firefox/120.0
Steps to reproduce:
Select email
Contextual menu - select 'Open Message in New Window'
Actual results:
Opening email replaces an exisiting email already open in a window
Expected results:
New email opens in a new window without affecting exisiting email window.
(This has been an irritant for previous versions of TB,, had hoped it would have been fixed by now)
CORRECTION (not allowed to edit above text):,
Issue occurs when double-clicking on the new email (not by using contextual menu).
Only way to open new email in new window is by using contextual menu, but not always easy to remember to use the contexual menu instead of habitually double-clicking!
Have you checked your settings?
Open messages in: [ ] A new tab [x] A new message window [ ] An existing message window.
Select the second option.
(In reply to Francesco from comment #2)
Have you checked your settings?
Open messages in: [ ] A new tab [x] A new message window [ ] An existing message window.
Select the second option.
Thanks for that but sadly the setting doesn't 'stick' - the moment I move away from TB app or quit app it reverts back to 'An exisiting message window' !
Where does the setting for this gets stored? Is it possible to manuallly change in a preference file?
The pref is mail.openMessageBehavior:
0 - open it in a new window
1 - open it in an existing window
2 - open it in a new tab
If that gets reset, there's something wrong with your system, perhaps a rogue add-on.
(In reply to Francesco from comment #4)
The pref is mail.openMessageBehavior:
0 - open it in a new window
1 - open it in an existing window
2 - open it in a new tabIf that gets reset, there's something wrong with your system, perhaps a rogue add-on.
Thanks, that worked!
Updated•7 months ago
|
Comment 7•4 months ago
|
||
zaggie, does this still reliably reproduce?
I think we have other reports of prefs not being correctly saved/reverting.
I have worked around by manually updating setting in prefs.js file
Updated•4 months ago
|
Description
•