<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Hey Madhava,<br></div><div><br></div><div>Thanks for looping us in. We have been quite involved in the Fx Reset conversations over the last few months. It is an extremely exciting project and one that I think we are not leveraging nearly to its full potential. Some this came from an awesome conversation I had with Asa a few months back. We see three basic layers in our fight for Recoverability:<br></div><div><ol><li>Proactively protect our users so that they don't experience problems in the first place (or fix the problem before the user notices)<br></li><li>If we fail at #1, ensure that we are empowering our users to self recover in the least painful and destructive ways possible.<br></li><li>If the user fails at self recovery (it will happen no matter how hard we work), point the user to a friendly place to seek 1 on 1 help aka SUMO<br></li></ol>For our 1st layer of Recoverability, we could perhaps run a check on places.sqlite after each update to ensure we haven't decimated the user's bookmarks, perform periodic database cleanups, remove old addon-compat overrides, monitor ballooning cache sizes, etc. All of these things can and should be done without user initiation. There are quite a few other suggestions that we've tossed around as well, but I don't want to get too deep into the weeds here. We also lack the Engineering chops to know what is and is not possible, so I'd LOVE LOVE to discuss in further detail with some of the big brains on this thread. <br></div><div><br></div><div>In the 2nd layer of Recoverability, what we had envisioned was having FHR present a very strategic list of suggested fixes based on the data we extract. This list may offer suggestions like disabling a particular add-on that causes slowness, crashes, excessive memory use etc or alerts the user if select about:config values have been changed to non-default values. Some of these items are currently covered in FX Reset, but we'd offer them as more surgical fixes. I'd even like to see information from <a href="http://www.mozilla.org/en-US/plugincheck/" data-mce-href="http://www.mozilla.org/en-US/plugincheck/">plugincheck</a>, as well as out of date graphics card drivers with links to updates if that were possible. This would give the user the option to take a very methodical and surgical approach to recovering. In the event that these steps fail, or for users that don't care to be surgical, we could also offer the "Full" Firefox Reset. We are working on making the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=833943" data-mce-href="https://bugzilla.mozilla.org/show_bug.cgi?id=833943">Fx Reset less destructive</a>, but by nature a reset results in loss of customization. For some users the time savings may be worth the mild discomfort. Others may still prefer the meticulous approach. <br></div><div><br></div><div>Finally, if the user simply cannot self recover we would direct them to SUMO where they can get the 1 on 1 support they would need.<br></div><div><br></div><div>I think that was a very roundabout way of answering your question. Let me know if you'd like to set something up to discuss in greater detail. We are always happy to help!<br></div><div><br></div><div>Matt<br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Madhava Enros" <madhava@mozilla.com><br><b>To: </b>"Mike Connor" <mconnor@mozilla.com><br><b>Cc: </b>"Alex Keybl" <akeybl@mozilla.com>, "Asa Dotzler" <asa@mozilla.com>, "Firefox Dev" <firefox-dev@mozilla.org>, "Matthew Grimes" <mgrimes@mozilla.com>, tdowner@mozilla.com<br><b>Sent: </b>Monday, July 8, 2013 1:53:03 PM<br><b>Subject: </b>Re: Reset Firefox -> Repair Firefox<br><div><br></div><div><span style="font-size: 15px;" data-mce-style="font-size: 15px;">For sure - as soon as you have a button for users to press that is essentially the "Work Properly" button, the question presents itself: why do we wait for them to press it.</span></div><div><span style="font-size: 15px;" data-mce-style="font-size: 15px;"><br></span></div><div><span style="font-size: 15px;" data-mce-style="font-size: 15px;">Matt Grimes and Tyler Downer have been thinking on this subject; I know they mentioned ideas for future "milder" versions of Firefox Reset that we could be running periodically automatically.</span></div><div><span style="font-size: 15px;" data-mce-style="font-size: 15px;"><br></span></div><div><span style="font-size: 15px;" data-mce-style="font-size: 15px;">Madhava</span></div><div><div><br></div><div>-- </div><div>Madhava Enros</div><div>Firefox User Experience</div><div>mozilla.org/firefox</div><div><br></div></div><p style="color: #A0A0A8;" data-mce-style="color: #a0a0a8;">On Monday, July 8, 2013 at 4:42 PM, Mike Connor wrote:</p><blockquote style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" data-mce-style="border-left-style: solid; border-width: 1px; margin-left: 0px; padding-left: 10px;"><div><div><div>On 2013-07-08 3:04 PM, Alex Keybl wrote:</div><blockquote><div><blockquote><div>I think we'd be better off calling this feature "Repair Firefox".</div></blockquote><div>The only issues I see here is that Repair Firefox implies a guaranteed solution, while a reset is just a tool that may help. Also, users may wonder why we don't always attempt a repair on launch every time, if there's no negative consequences.</div></div></blockquote><div>If we're going to do something like this we should really find a way of</div><div>a) doing this incrementally and in-process and b) based on detection of</div><div>problematic states. That would leave the manual "big reset button" to</div><div>cover the cases we can't automatically detect/fix. (And we should track</div><div>those resets, maybe in FHR, to get a handle on how much it's still</div><div>necessary.)</div><div><br></div><div>-- Mike</div><div><br></div><div><br></div><div>_______________________________________________</div><div>firefox-dev mailing list</div><div><a href="mailto:firefox-dev@mozilla.org" target="_blank" data-mce-href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a><br></div><div><a href="https://mail.mozilla.org/listinfo/firefox-dev" target="_blank" data-mce-href="https://mail.mozilla.org/listinfo/firefox-dev">https://mail.mozilla.org/listinfo/firefox-dev</a><br></div></div></div></blockquote><div><br></div></div><div><br></div></div></body></html>