On 1/8/2021 6:35 PM, Ray Davison wrote: > David E. Ross wrote: > >> >> Browser sessions are saved according to the preference variable >> browser.sessionstore.interval >> which has the default value of 15000. The units are milliseconds; thus >> the default is 15 seconds. > > 1500 >> >> If you have multiple tabs open, the number of tabs that can be restored >> concurrently is controlled by the preference variable >> browser.sessionstore.max_concurrent_tabs >> which has the default value of 3. > -1 >> >> However, the maximum number of tabs that can be restored is controlled >> by the preference variable >> browser.sessionstore.max_tabs_undo >> which has the default value of 10. > 10 >> >> You might want to examine those three preference variables via >> about:config >> You might be terminating when you opened tabs later than the most recent >> save. >> >> Also look at preference variables >> browser.sessionstore.resume_from_crash > true >> and >> browser.sessionstore.resume_session_once >> If the first has the value "false" (not the default "true"), restoring >> after a crash is blocked. If the second has the value "true" (not the >> default "false"), the first restore of a session prevents later restores >> of the same session. > false >> > Everything is default except that -1. > > Does upper right corner "Close" > "Save and close", save anything when > clicked, or does it only save what some background process has already > saved. > > At the next app run, it saved all or nothing. > > Ray
Windows 7 SeaMonkey 2.49.5 For me, saving occurs as controlled by browser.sessionstore.interval while SeaMokey is still active. I seem not to have a "Save and Close" capability. -- David E. Ross <http://www.rossde.com/> I just do not understand why so many people think a sore loser makes a great President. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
