Comment 84 for bug 230102
Revision history for this message
|
|
#84 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
A small remark: I've seen that the current behavior of FF3.0 (not showing a warning on close when session restore is enabled, regardless of "warn on close" option) was reported as a bug in some Mozilla-related online communities (I moderate one in livejournal and I saw such postings there).
I'd like to add my vote for allowing the user to have a warning even if session restore is enabled. The cases when it is useful are at least the following:
1. Having a form n a web page partially filled. Text in form controls is NOT restored by a built-ib session manager.
2. Having a HTTP auth in some tabs. When restoring, users have to authorize again (if password is not saved, that may take some time).
3. Using some AJAX-heavy sites where session manager can fail restoring the tab(s) state correctly.
Case 1 is especially important because it is a potential data loss - the exact case the "warn on close" pref was designed to prevent. I myself encountered similar problems when typing a long comment in livejournal or bugzilla, then closing my session, then losing the typed text on restart.