Closed Bug 1278038 Opened 8 years ago Closed 8 years ago

email views are not persistent across launches

Categories

(Thunderbird :: Mail Window Front End, defect)

46 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: astronaut, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.85 Safari/537.36

Steps to reproduce:

Top field with message listing is not persistent across launches. Change the default into your preferences, like selecting from, recipient, ordering fields the way you like, quit and relaunch, all your work is lost, and you have to do it again.

Versiosn 41.1, 41.1.1, 46a - version 37 does not have this bug


Actual results:

Top field with message listing is not persistent across launches. Change the default into your preferences, like selecting from, recipient, ordering fields the way you like, quit and relaunch, all your work is lost, and you have to do it again.

Versiosn 41.1, 41.1.1, 46a - version 37 does not have this bug


Expected results:

Top field with message listing is not persistent across launches. Change the default into your preferences, like selecting from, recipient, ordering fields the way you like, quit and relaunch, all your work is lost, and you have to do it again.

Versiosn 41.1, 41.1.1, 46a - version 37 does not have this bug
Do you use mnenhy? There are some known extensions which aren't compatible. If you haven't mnenhy, please try to deactivate all extensions and check if the issue still happens.
no extensions at all. as mentioned version 37 does not have this bug. version 41, 41.1.1 makes thunderbird almost unusable. also another important security bug i reported, version 37 is ok. https://bugzilla.mozilla.org/show_bug.cgi?id=1278039
like bug 1278039, safe mode should be tested
solved with no addons, layout is now persistent across relaunches of thunderbird, earlybird app
Thanks for the update
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.