Firefox/Projects/Automatic Recovery: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
The purpose of this project is to reframe how Firefox deals with failures.<br> | The purpose of this project is to reframe how Firefox deals with failures.<br> | ||
'''Currently our process is:'''<br>-The user notices undesirable symptoms (like "firefox won't start").<br>-The user has to seek out the solution on their own (go to a support form, learn about safe mode, follow the various steps). | '''Currently our process is:'''<br>-The user notices undesirable symptoms (like "firefox won't start").<br>-The user has to seek out the solution on their own (go to a support form, learn about safe mode, follow the various steps). | ||
| Line 13: | Line 11: | ||
<br> | <br> | ||
The idea is to apply this model of automatic recovery to as many errors as we can, launching into Safe Mode is just one instance of the new approach.<br> | The idea is to apply this model of automatic recovery to as many errors as we can, launching into Safe Mode is just one instance of the new approach. Here is another example: {{bug|513419}}<br> | ||
== Current Status == | == Current Status == | ||
| Line 34: | Line 32: | ||
{{bug|347680}} | {{bug|347680}} | ||
{{bug|513419}} Close Firefox dialog | |||
<br> | |||
== Team == | == Team == | ||
| Line 45: | Line 44: | ||
(otherwise the project as a whole is currently inactive)<br> | (otherwise the project as a whole is currently inactive)<br> | ||
<br> | |||
== Designs == | == Designs == | ||
| Line 57: | Line 56: | ||
*Firefox "Just Works," even when it is actually rather broken.<br> | *Firefox "Just Works," even when it is actually rather broken.<br> | ||
<br> | |||
== Non Goals == | == Non Goals == | ||
Revision as of 04:52, 29 August 2009
Summary
The purpose of this project is to reframe how Firefox deals with failures.
Currently our process is:
-The user notices undesirable symptoms (like "firefox won't start").
-The user has to seek out the solution on their own (go to a support form, learn about safe mode, follow the various steps).
Proposed approach:
-Firefox detects what is happening (notices that it crashed repeatedly and before displaying about:sessionrestore)
-Firefox automatically takes the logical course of action (launches into safe mode).
The idea is to apply this model of automatic recovery to as many errors as we can, launching into Safe Mode is just one instance of the new approach. Here is another example: bug 513419
Current Status
Complete
- Automatically restart on crash (fixed in Shiretoko)
- Auomatically show about:sessionrestore on two start up crashes (Fixed in Shiretoko)
Next Steps
- Automaticaly launch into Safe Mode when about:session restore can't even load (third sequential start up crash).
- Identify additional areas where where we can do an automated recovery (fourth start up crash? locked places file? etc.)
Related Bugs
bug 347680 bug 513419 Close Firefox dialog
Team
Simon Bünzli: about:sessiorestore
Michael Kohler: launching into safe mode
(otherwise the project as a whole is currently inactive)
Designs
Automatically dealing with start up crashes (kind of old, but shows general idea)
Goals/Use Cases
- Firefox "Just Works," even when it is actually rather broken.
Non Goals
- Telling the user what went wrong on a implementation level
- Telling the user how Firefox works or should work on an implementaiton level
- Telling the user what support articles they need to read
- Telling the user what steps they need to take
- Branding a tool for recovery (like calling it "Safe Mode")