2
edits
Talk:Session Restore: Difference between revisions
Jump to navigation
Jump to search
→Unresolved questions
LukeKendall (talk | contribs) |
|||
| Line 107: | Line 107: | ||
''Make sure that if the state of the current session crashes the browser, it | ''Make sure that if the state of the current session crashes the browser, it doesn�t reload at startup and crash over and over again. Look into how SessionSaver and Total Recall detect this.'' | ||
* Whats really helpful would be a FF extension and page processing calls log that can be relied upon to note extension calls made (and their successful return) and page render or page processing calls made (and their successful completion). In theory when it crashes, very few extensions or pages will actually have commenced a call but not completed. Those will likely be the problem ones. beyond that its a problem with FF core code, and a safe start or debug session. The core of the problem is having a way to narrow down problematic pages and extensions. Perhaps if it crashes during a restore it offers to switch to a "safe restore" mode (as opposed to "safe mode"), where extensions are loaded one by one, then pages loaded one by one, and the cause of the crash identified and reported for debugging? Ie a fallback mode for restore where the user gets a slower restore, that keeps as many pages and extensions as it can alive. [[User:Foxxen2|Foxxen2]] 09:24, 30 March 2006 (PST) | * Whats really helpful would be a FF extension and page processing calls log that can be relied upon to note extension calls made (and their successful return) and page render or page processing calls made (and their successful completion). In theory when it crashes, very few extensions or pages will actually have commenced a call but not completed. Those will likely be the problem ones. beyond that its a problem with FF core code, and a safe start or debug session. The core of the problem is having a way to narrow down problematic pages and extensions. Perhaps if it crashes during a restore it offers to switch to a "safe restore" mode (as opposed to "safe mode"), where extensions are loaded one by one, then pages loaded one by one, and the cause of the crash identified and reported for debugging? Ie a fallback mode for restore where the user gets a slower restore, that keeps as many pages and extensions as it can alive. [[User:Foxxen2|Foxxen2]] 09:24, 30 March 2006 (PST) | ||
| Line 113: | Line 113: | ||
''Should form state include saving checkbox and selectbox state as well as text input?'' | ''Should form state include saving checkbox and selectbox state as well as text input?'' | ||
* Yes. See above, re text box contents, same applies. [[User:Foxxen2|Foxxen2]] 09:24, 30 March 2006 (PST) | * Yes. See above, re text box contents, same applies. [[User:Foxxen2|Foxxen2]] 09:24, 30 March 2006 (PST) | ||
''If there are multiple windows open, how do we decide what was the last session? The last window closed, or the last group of windows?'' | |||
* If they're all exited together, by quitting from FF, the answer is clearly that all should be saved. | |||
* But I think better would be to have an explicit Save Session and Restore Session function. Then the semantics can simply be to hold the session for auto reload (or prompted reload) after a crash; but normally to require an explicit Restore Session action by the user. | |||
[[User:LukeKendall|LukeKendall]] 10:20, 18 July 2006 (EST) | |||
== Crash Recovery and Session Manager have good code == | == Crash Recovery and Session Manager have good code == | ||