Closed Bug 368698 Opened 13 years ago Closed 13 years ago
Preference appearance startup does not allow Mail and News Groups as preference
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11pre) Gecko/20070111 SeaMonkey/1.1 Build Identifier: Sea Monkey 1.1 After choosing Mail and News Groups as Preference for Appearance Startup, I expected to enter SeaMonkey in Mail and News Groups. It worked for about 3 startups, then went back to starting in Navigator. I have tried reselecting the preference but can no longer get SeaMonkey to start in Mail and News Groups instead of Navigator. (I prefer to check email before going to Navigator). Thank you Reproducible: Always Steps to Reproduce: 1.Select Edit > Preference in Mail and Newsgroups or Navigator 2.Click Appearance > and check Mail and News Groups under "When SeaMonkey starts up, open: 3.3 times SeaMonkey started up in Mail and News Groups. Actual Results: After 3 starts it defaulted back to starting up in Navigatof Expected Results: SeaMonkey starts up in Mail and News Groups instead of Navigator Software should have retained the selected Appearance Preference
Do you mean that you start the program three times without exiting, or three times of start, exit, start... ?
Diane responded in email: I mean 3 times of start, exit, start, exit. I tested it several times to be sure I had actually been able to set the preference. I think i lost the preference I'd set, after I shut down my computer for the day. When i started seamonkey up the next morning it started up in navigator and I was no longer able to reset the preferences. Now it always starts in navigator no matter how I set the preferences (whether I set them to composer or address book, or mail and news groups). ========================= Are you using QuickStart? (On the Preferences|Advanced page.) (Please respond in the bug, not in email.)
Not using QuickStart. I had it set to JavaEnabled. I just tried Quick Start but the problem still exists.
Any progress on this bug? Diane Hartman
Thank you so much - just got 1.1.1. Problem fixed. Appreciate it.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.