If the user has checked the Always report crashes option or
equivalent, or once the user has clicked Report this crash, that sound
like a good idea.
On 10/07/14 02:18, Tobias B. Besemer wrote:
So maybe a other option for a resolution:
A msg to the user after the restart of FF that a
Interesting point. What's the profile of users who write comments on
crash reports? Would they click on a button add comments?
On 08/07/14 21:33, Honza Bambas wrote:
This would probably eliminate most comments we get on crash reports.
Even if a good number of those are not helpful now, a
Most probably would not type a comment when they're not immediately
prompted for it. We could do an experiment around it, but I'd be
surprised if anything else comes out of it.
I for myself probably wouldn't type a comment myself in 90% of the
cases when that was required, and I know how
On 7/9/2014 4:46 PM, Robert Kaiser wrote:
Most probably would not type a comment when they're not immediately
prompted for it. We could do an experiment around it, but I'd be
surprised if anything else comes out of it.
There's no reason to guess or use personal anecdotes for this. We'll do
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
Am Samstag, 5. Juli 2014 14:21:47 UTC+2 schrieb David Rajchenbach-Teller:
[...]
3. Crash report is stored to disk, without any dialog;
4. If the crash happened during Firefox shutdown, do nothing, otherwise
restart Firefox to its previous state (obviously, we need some measure
to prevent this
On 08/07/14 16:25, Tobias Besemer wrote:
Am Samstag, 5. Juli 2014 14:21:47 UTC+2 schrieb David Rajchenbach-Teller:
[...]
3. Crash report is stored to disk, without any dialog;
4. If the crash happened during Firefox shutdown, do nothing, otherwise
restart Firefox to its previous state
On 7/7/14 12:21 PM, Ehsan Akhgari wrote:
We should keep in mind that sometimes due to startup crashes, we don't
get to run any of the code in Firefox, so we can't gate the crash report
submission on that code at least in the case of startup crashes.
Yes. For that, I think we'll need to retain
- 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
Am Dienstag, 8. Juli 2014 18:23:00 UTC+2 schrieb Justin Dolske:
2) Being able to integrate the crash-submission flow into the browser
opens up possibilities for better UX and features, since it's the
familiar cross-platform environment we all work in.
Sorry, maybe a little bit OT ... ;-)
On 7/5/2014 8:21 AM, David Rajchenbach-Teller wrote:
Could we redesign this as follows?
1. Something goes wrong in the code of Firefox;
2. Firefox dies;
3. Crash report is stored to disk, without any dialog;
4. If the crash happened during Firefox shutdown, do nothing, otherwise
restart
On 7/8/14 9:56 AM, Tobias Besemer wrote:
Am Dienstag, 8. Juli 2014 18:23:00 UTC+2 schrieb Justin Dolske:
2) Being able to integrate the crash-submission flow into the browser
opens up possibilities for better UX and features, since it's the
familiar cross-platform environment we all work in.
Am Dienstag, 8. Juli 2014 20:40:13 UTC+2 schrieb Justin Dolske:
On 7/8/14 9:56 AM, Tobias Besemer wrote:
Am Dienstag, 8. Juli 2014 18:23:00 UTC+2 schrieb Justin Dolske:
2) Being able to integrate the crash-submission flow into the browser
opens up possibilities for better UX and
David Rajchenbach-Teller schrieb:
5. Upon the next restart, display a bottom doorhanger on all windows
Firefox or an add-on encountered a problem [a few seconds ago / on July
4rd, 2014] and recovered. If you wish, Firefox can report it
automatically so that we can fix the bug report/not this
Justin Dolske schrieb:
3) E10S will already need something vaguely like this
That's a completely different subject, esp. as we already have an
in-content crash reporter UI for plugin crashes.
KaiRo
___
dev-platform mailing list
On 7/8/2014 21:23, Robert Kaiser wrote:
David Rajchenbach-Teller schrieb:
5. Upon the next restart, display a bottom doorhanger on all windows
Firefox or an add-on encountered a problem [a few seconds ago / on July
4rd, 2014] and recovered. If you wish, Firefox can report it
automatically so
Tobias Besemer schrieb:
Sorry, maybe a little bit OT ... ;-)
Would it be possible to report back to Mozilla hanging scripts ???
I'd love to have something reporting fatal JS error and hanging scripts
but that would be something pretty different from what the current crash
reporter does as
We should keep in mind that sometimes due to startup crashes, we don't
get to run any of the code in Firefox, so we can't gate the crash report
submission on that code at least in the case of startup crashes.
Cheers,
Ehsan
On 2014-07-05, 8:21 AM, David Rajchenbach-Teller wrote:
I haven't
On 07/07/14 21:21, Ehsan Akhgari wrote:
We should keep in mind that sometimes due to startup crashes, we don't
get to run any of the code in Firefox, so we can't gate the crash report
submission on that code at least in the case of startup crashes.
Cheers,
Ehsan
Yes, we clearly need to
I haven't experienced crashes in some time, so I may have missed some
redesigns, but last time I did, the crash experience looked as follows:
1. Something goes wrong in the code of Firefox;
2. Firefox dies;
3. Crash Reporter appears;
4. Eventually, if the user has clicked restart, Firefox
20 matches
Mail list logo
