Session Manager 0.1 to 0.3.9+Can someone tell me if it is one of my (Macintosh) FF extension preferences or a FF "feature" where FF will quit when you close all of its windows?
Feature, preference or not, Session Manager apparently does not save my current session when this happens. All my tabs at the time I close the window are not restored upon relaunch of FF. FWIW, for what I have installed, I searched through what I thought might be the "appropriate" preferences that might address the quitting feature, i.e., Mr Tech Local Install and Tab Mix Plus, and even FF's own preferences, but I didn't notice anything. Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:48.0) Gecko/20100101 Firefox/48.0
@dougeeebear: This only affected cookies - and has been fixed as of today's testing version.
<a href="http://www.haslo.ch/zeniko/software/sessionmanager-dev.xpi">Today's testing version</a> (0.3.9.10+) also introduces support for Firefox Preloader. Should anybody use that, please test that it now works correctly. @anon42: If you're using version 0.3.9, please update to the current testing version and try again.
Sorry about the hack part. I did not look at it until after I posted. I had assumed the menu was due to a new version. That is working. Your about:config entry is missing. I do have extensions.crashrecovery.resume_session set to false. Could you have entered the wrong entry name? extensions.crashrecovery.resume_session_once is also false. extensions.crashrecovery.restore_prompt_uri is set to "chrome://sessionmanager/content/restore_prompt.xul". Will Pittenger
Just tried it. Thanks. It now restores the tabs that were in effect when I click the close window. ![]() Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:48.0) Gecko/20100101 Firefox/48.0
I have to disagree. Unless something like bookmarks or About:config entries are not saved when changes are made, the mainstream developers need not concern themselves with a crash when the program is supposed to be closing anyway along with the rest of Windows. In fact, I have have to believe that only extensions that save the session need to deal with that. What can you do? Complain to the people who can fix it. Will Pittenger
Today's <a href="http://www.haslo.ch/zeniko/software/sessionmanager-dev.xpi">testing version</a> (0.3.9.11+) is the first release candidate for version 0.4. If no more issues show up, I'll release it around the beginning of next week.
What version are you using? The pref extensions.crashrecovery.restore_prompt should show up since around version 0.3.9.8+. If it doesn't show up, you'll have to create it yourself (right-click -> New -> Boolean).
The problem is that for an OS independent extension there is no way to tell that the OS is shutting down. Extensions are only informed when Firefox is quitting. If that notification isn't correctly sent, that's an issue with Firefox.
This has already been done: bug 333907. My version is 0.3.9.
Will Pittenger
Working great for me. Only one little tiny issue: when you add the "Undo Close" button to the toolbar, the separator below Session Manager Options in the Session Manager toolbar button's menu is still there. Btw, I am referring people who want session restoring capability in superT to your extension. ![]() and I voted for bug 333907.
I seem to be getting something similar, with SM 0.3.9 and Firefox 1.5. I typically have a single window and 15 to 20 tabs; I can restore closed windows, but not tabs. When I closed a tab, I got this on the JS console:
Then you'll have to either create the pref by hand or update to the testing version (as I already told you) or create the pref yourself.
Thanks for the note. That's fixed in <a href="http://www.haslo.ch/zeniko/software/sessionmanager-dev.xpi">today's update</a> (0.3.9.12+).
Thanks for the error message. I'm still not able to reproduce this issue. However I've made several adjustments which hopefully mitigate this issue. Please try the current <a href="http://www.haslo.ch/zeniko/software/sessionmanager-dev.xpi">testing version</a> and verify that it doesn't happen any longer. ok, this is odd. After a few sessions, the error disappeared and SM is working as expected. o.O Oh well. Hope the error message at least helped you catch something
![]() After testing SM built-in older session backup operation v/s the userChrome.js version, here is what I conclude after a crash (with older session backups to keep set at '1'):
SM built-in version entries at startup after a crash: > [ Crashed Session... ] > [ Older Browsing Session... ] > [ Previous Browsing Session ] After one restart: > [ Crashed Session... ] > [ Previous Browsing Session ] "Older Browsing Session" is gone and "Crashed Session" is still the Crashed Session. (unexpected operation) After another restart: > [ Older Browsing Session... ] > [ Previous Browsing Session ] Back to normal. userChrome.js version entries at startup after a crash: > [ Crashed Session... ] > [ Older Browsing Session... ] > [ Previous Browsing Session ] After one restart: > [ Older Browsing Session... ] > [ Previous Browsing Session ] "Crashed Session" is gone, back to normal (expected operation) So to me, the userChrome.js version makes more sense, and is what I am using instead of the built-in version. I'm currently using SM version 0.3.9.11+.
Actually, you can't use the userChrome.js version instead of the built-in one. What you observed works only for one backup copy - all others are deleted by Session Manager (as you told it by setting the number of additional backups to 0). If you want to discuss this further, please do so over at the new discussion thread. Since version 0.4 is out and I prefer to keep the thread to a reasonable length:
Return to Extension Development Who is onlineUsers browsing this forum: No registered users and 1 guest |
![]() |