Open Bug 685731 Opened 9 years ago Updated 2 years ago
Be more diligent about saving and restoring sessions when doing updates
When Firefox has an update, we're pretty intrusive about making sure users update, by notifying over and over. Unfortunately, if there is a session storage bug or if the user is in private browsing or has the browser set to delete history on close, we may actually end up losing all of a user's tabs and open form history (sometimes irrecoverably). If possible, we should figure out what's causing this dataloss and fix it but minimally, we should detect if we're not likely able to save their session and warn accordingly or take extra steps to try to recover.
Are these reports only affecting Firefox 6 on Mac?
Verified: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0) Gecko/20100101 Firefox/7.0 Updated from Fx6b5 and Fx6.0.2 to Fx7b5. All the tabs were restored fine under several different conditions: in normal mode - remember history, in normal mode - delete history on close, in private browsing, immediately after another restore, manual upgrade, automatical upgrade. The only issue that did reproduce was: 1. Launch Fx 6b5. 2. Set Fx to clear history when it closes. 3. Open a shopping web page. 4. Add some item to the cart. 5. Open Help->About to automatically upgrade Fx. After the upgrade, the page was restored, but the items from the shopping cart were no longer there.
(In reply to Ioana Budnar [QA] from comment #2) > After the upgrade, the page was restored, but the items from the shopping > cart were no longer there. This could very well be related to the web page itself. If your shopping cart contents are stored via cookie I would assume this to restore. However, some sites (especially ajax/flash sites) may not work 100%. Though it begs further investigation. What site were you using to test shopping cart retention?
I just suck at remembering to change the platform info when I file bugs. This probably affects everyone based on the underlying session restore bugs. A couple specific things come to mind: 1) We may want to warn users who are using private browsing before we do an update. 2) Ditto if they have Firefox set to delete settings on exit. 3) Fix underlying session restore bugs or make updates do something completely special which gets around potential issues with writing to sessionstore.js
OS: Mac OS X → All
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #3) > ... What site were you using to test shopping cart retention? I used and amazon.com and emag.ro. The issue reproduced with both of them.
Question is, what shopping cart technologies (and back-end technologies) do these sites use? and do those technologies have APIs which give Session Store visibility into the data for saving.
You need to log in before you can comment on or make changes to this bug.