Re: SM 2.24 browser multi-tab session restore failure
Paul B. Gallagher wrote, On 2014.03.07 22:12: User wrote: Summary - SM 2.24 browser does not always save a full snapshot of a browser tab and this results in some web sites having to be re-logged in again after session restore. ... I have checked my CLEAR PRIVATE DATA settings in PREFERENCES, I previously had it set to auto clear private data but the only data I selected to clear was browser cache contents, which did not affect the older version SM 2.21 in always being able to fully restore all browser tabs without having to log in. But in SM 2.24, even though I have the CLEAR PRIVATE DATA disabled, this problem is not resolved and I believe the problem has to do with how SM 2.24 saves browser tab contents that is causing certain tabs with log in data to be lost in the session save. One possibility -- which only you can check -- is that the cookies in question expired in the interim. Not all cookies are designed to last until 2039. So if you restored after their expiration date, the expired cookies would be rejected by the server and it would ask you to login again. Also worth looking at your cookie defaults and site-specific permissions -- if you're only accepting session cookies, they should not survive a program termination (by definition), even if you don't have SM set to clear cookies on termination. There may be other possibilities I haven't thought of. Keep reading. Your points are valid. However, the session restore usually happens within less than 15 SECONDS of shutting down the SM application. The most I usually leave it is maybe 10 to 15 minutes at best. So expiry isn't the cause. I also haven't changed any cookie permission settings since upgrading from SM 2.21 to 2.23. It just suddenly stopped working for some sites that needed the log in information to be retained, whatever that might be. I've selected the option to accept all cookies and accept them all normally. I think I'll try to clear all cookies for specific sites that are having problems and then see how it fairs. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
SM 2.24 browser multi-tab session restore failure
Summary - SM 2.24 browser does not always save a full snapshot of a browser tab and this results in some web sites having to be re-logged in again after session restore. I recently upgraded from SM 2.21 to SM 2.24. In general, everything works fine on 2.24, the upgrade was smooth as usual. However, I have noticed that SM 2.24's browser tab restore now fails with some content where 2.21 did not fail before. This involves sites which requires log in. Often, I may close the SM browser with several tabs open, and then also close all other SM related windows to completely shut down the application, wait 5 to 10 seconds and then restart the SM browser window. This practice releases Windoww system resources and any potential memory leaks, as well as stops the SM mail client from checking e-mails at multiple accounts that I typed my password into during the last session (i.e. no more new mail check / alerts to disturb the user). With this practice, the first web site that SM 2.24 browser failed to fully save its state is with OUTLOOK.COM. Previously with SM 2.21, when the session was restored (anywhere from 10 seconds to 10 or 15 minutes after closing the browser with multiple tabs and saving the session), I was able to get back into outlook.com web mail without having to re-login again. However, with SM 2.24, it seems to discard some private information and when I restore the multi-tab browser session, I am prompted by outlook.com to re-login again. Does anyone know what has changed in the browser session save that may cause SM 2.24 browser to leave out some parts of private data that would cause a failure of full browser tab restore with scenarios such as this? I have other web sites that requires log in and SM 2.24 restored them without problems but it seems that SM 2.24 is not saving some parts of the browser tab in the session snapshot which causes some sites to re-prompt for login again after browser session restore. If anyone using outlook.com could test this problem by first logging into their outlook.com web mail account, then opening multiple tabs, closing the SM 2.24 browser to save all tabs and then restarting the browser to see if they could regain access to outlook.com web mail, I would appreciate hearing any feedback / confirmations of this problem. I have checked my CLEAR PRIVATE DATA settings in PREFERENCES, I previously had it set to auto clear private data but the only data I selected to clear was browser cache contents, which did not affect the older version SM 2.21 in always being able to fully restore all browser tabs without having to log in. But in SM 2.24, even though I have the CLEAR PRIVATE DATA disabled, this problem is not resolved and I believe the problem has to do with how SM 2.24 saves browser tab contents that is causing certain tabs with log in data to be lost in the session save. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.24 browser multi-tab session restore failure
User wrote: Summary - SM 2.24 browser does not always save a full snapshot of a browser tab and this results in some web sites having to be re-logged in again after session restore. ... I have checked my CLEAR PRIVATE DATA settings in PREFERENCES, I previously had it set to auto clear private data but the only data I selected to clear was browser cache contents, which did not affect the older version SM 2.21 in always being able to fully restore all browser tabs without having to log in. But in SM 2.24, even though I have the CLEAR PRIVATE DATA disabled, this problem is not resolved and I believe the problem has to do with how SM 2.24 saves browser tab contents that is causing certain tabs with log in data to be lost in the session save. One possibility -- which only you can check -- is that the cookies in question expired in the interim. Not all cookies are designed to last until 2039. So if you restored after their expiration date, the expired cookies would be rejected by the server and it would ask you to login again. Also worth looking at your cookie defaults and site-specific permissions -- if you're only accepting session cookies, they should not survive a program termination (by definition), even if you don't have SM set to clear cookies on termination. There may be other possibilities I haven't thought of. Keep reading. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
