mrtech wrote:from my point of view you did provide an option with earlier versions and now that has been pulled.
And from mine, I've provided a hack in earlier version and now managed to implement it more cleanly (so that other extensions don't have to be aware of Crash Recovery and can still take advantage of it).
mrtech wrote:Help me understand, is this affecting only 2.0 and newer builds? what changed in CR/SM? Are you currently disabling 2.0 and newer session management and implementing yours?
This only affects version containing the fix to
bug 335864. The only change is that on "quit-application" CR sets the resume_session_once pref if the quit reason is "restart". And I currently disable Firefox 2's session saving service, because it doesn't yet provide any additional value to Session Manager.
Just note that Crash Recovery probably won't ever officially support Firefox 2 and I'm not yet sure whether I'll rewrite Session Manager for Firefox 2 or if I'll just pull the plug. And anyway, Firefox users are currently not affected by any of this at all.
Finally, you still do have the option to not resume the session: by not leaving anything to be restored. Just close all tabs/windows except a blank one before the restart (or alternatively, just delete the file crashrecovery.dat/sessionstore.ini at/after the "quit-application" notification).
XerBlade wrote:Because I also use it to quickly end my current cookie sessions on several websites at once while still continuing to use Firefox. There would be no point to this if the session were restored.
Interesting reason, but nothing you couldn't better achieve through "Clear Private Data...".
XerBlade wrote:(for example: when clearing Firefox's memory footprint after doing a rather intensive task using lots of tabs simultaneously).
For the second case, there's the option "Close Other Tabs". As for the first case, you've got a point there. I'll think about how important that edge case is to me. Thanks for the input.