On 07/07/14 22:09, Ted Mielczarek wrote: > I believe this was the primary reasoning behind the current > implementation (it's been a while, I'm a little fuzzy). We need to > handle startup crashes, so we need the native crashreporter UI > regardless of whether we build an in-product crash reporting UI.
This absolutely makes sense. [...] > It's also worth noting that our behavior matches the behavior of > existing OS platform crash reporters--on all the OSes I'm aware of > there's a dialog similar to our own, so it's not an unfamiliar workflow > to users. That being said the crashreporter UX is essentially unchanged > from what we shipped in Firefox 3.0, so there's certainly room for > improvement! Note, however, that there is a big UX difference between what OSes do and what we do. Random OS: "Hey, look, *I* didn't crash, Firefox did." Firefox: "Hey, look, *I* crashed." which I suggest we turn into Firefox: "Oh, by the way, I recovered." Cheers, David -- David Rajchenbach-Teller, PhD Performance Team, Mozilla
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
