| Summary: | crash recovery: present replay page instead of immediately restoring page | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Maciej Pilichowski <bluedzins> |
| Component: | general | Assignee: | Eduardo Robles Elvira <edulix> |
| Status: | ASSIGNED --- | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Maciej Pilichowski
2008-07-11 21:09:14 UTC
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. |