User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0 In all builds up to and including FF3b5, firefox would ask if I wanted to save the open pages to be reopened the next time firefox started. After the RC1 update, it no longer asks, and does not do it. Reproducible: Always Steps to Reproduce: 1. Open Firefox. 2. Open a bunch of pages. 3. Select File->Exit and see if it asks whether you want to save your open pages. 4. Restart Firefox and see if it reopened them. Actual Results: I was not asked if I wanted to save my open pages, and they were not saved+restored. Expected Results: I should have been asked if I wanted to save my open pages, and it should have done so if I clicked Yes. If this doesn't repro for you, you may need to configure Firefox to use windows instead of tabs, as I do. (No offense, but I really, really dislike tabs.)
Update: Someone told me that I needed to have at least 'browser.tabs.maxOpenBeforeWarn' pages open before I'd be asked if I wanted to save my session. As the default value is 15, and as RC1 seems to be the first version that actually reads it, this explains why the feature suddenly stopped working. Setting that value to 1 returned me to b5 behavior. I think the real bug here is that the default for that value is 15. Shouldn't it be 1? 2 at most? Inconsistent behavior is the bane of a UI. Not asking with 14 open, but asking with 15, is inconsistent and confusing for a regular user. Heck, I'm a senior software engineer and I got confused.
No, browser.tabs.maxOpenBeforeWarn is something different. It controls the warning that will appear when you open a large number of tabs (if you bookmarked a group).
Component: Session Restore → General
QA Contact: session.restore → general
Version: unspecified → 3.0 Branch
You're right. The seeming fix was coincidental. Now when I set that value back to the default of 15, I'm still asked if I want to save my session on exit. What's interesting is that had I re-installed b5 over a copy of the RC1 folder so I could run either. I suspect that b5's installer changed some common data (profile?) back to something that works correctly.
This is a mass search for Firefox General bugs filed against version 3.0 that are UNCO and have not been changed for 200 days. Reporter, please update to Firefox 3.6.10 or alter. Firefox 3.0 is no longer supported and is no longer receiving updates. After you update, please create a fresh profile, http://support.mozilla.com/kb/managing+profiles, and test to see if your bug still exists. If you still the bug, then please post a comment with the version you tested against, and the problem. If the issue is no longer there, please set the RESOLUTION to RESOLVED, WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.