Version: (using Devel) Installed from: Compiled sources crash recovery: present replay page instead of immediately restoring page Currently when the crash occurs, and then restore, all pages are immediately restored. This is not always what user would like (not every page was really important, not all pages are useful to see now, etc). But imagine this: * user chooses restore (after crash, let's say www.google.pl was in session and www.kde.org) * two tabs are created, for first google for the second kde * instead of loading those pages konq. presents big ">" (and "restore" label?) button (in page), when clicked page is loaded This only is nice (imho) and convenient, but there is a lot of improvements around the corner. Konq could present: * date and time of the crash * option to close&remember this page (keep in crash log) * option to forget it (and do not load it) * thumbnail of the page (from crash log) Another approach is possible -- one page with "thumbnails" (or rather blocks, run fresh opera to know what I mean) for every page from crash, with ">" buttons, etc. This is much easier to pick up "the right" page then sift trough menu items with meaningless (in case of long addresses) info. This is maybe not a killer feature for expert, but very comforting one for beginners and intermediate users.
PS. One more thing -- info about status of the page before crash could be presented: fully loaded, when loading. It would be some indication which page caused a crash.
I like those ideas. I will try to find which of them I can develop for 4.2 =)
I am glad to hear that, thank you. Polishing thoughts -- I like the second approach better, it is more compact. And another advantages: * the restore dialog could be removed at all * GUI option for showing this page at startup --> near startup page in Konq. settings * additional button at this recovery page with "switch to start page" * removing crash plugin from Konq. menu (or rather crash menu items) in favor of this page All those steps would provide more compact Konqueror experience. And not about status (#1) -- instead of loaded/loading status this could be changed to "safe" (no icon) and "risky" (lighting icon for example). So it would fit nicely with mixed autosave -- on-change/on-load-completed for addresses (you will get full log with indication what could go wrong, this would also help because I could send a bug report about Konq more easily) and on-time for data input.