----- Original Message ----- > From: "Justin Dolske" <dol...@mozilla.com> > To: dev-platform@lists.mozilla.org > Sent: Tuesday, July 8, 2014 9:23:00 AM > Subject: Re: Rethinking the crash experience > > 3) E10S will already need something vaguely like this, since a > content-process crash won't take down the whole browser. (And having the > native crash report pop up would be weird.) I'm not sure if we know what > the content-vs-chrome breakdown will be for all crashes with E10S, but > I'd sorta assume content crashes would be more common, and that UX flow > will be the one seen more frequently by users.
This is the current UI we have for content process crashes: http://billmccloskey.files.wordpress.com/2013/10/e10s-2.png If a crash report is found, there's a checkbox that also appears asking whether to submit it. The user has to hit "Try Again" in order to submit the crash. We have bug 913651 open to improve the experience, but I don't think anyone is working on it. -Bill _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
