Open
Bug 445600
Opened 16 years ago
Updated 2 years ago
break up strings for crash dialog for better modularity and use
Categories
(Toolkit :: Crash Reporting, defect)
Toolkit
Crash Reporting
Tracking
()
NEW
People
(Reporter: chofmann, Unassigned)
Details
spin off from bug 444961
> re: comment 7
>
> Rather thank disabling all the crash submission controls is it possible to
> remove them from the dialog for the 90%? If the dialog just said:
>
> Firefox has encountered a problem and has crashed.
> We will try and restore your tabs and windows when you restart.
>
> [quit] [restart]
>
>
> that might work.
From some discussion today it sounds like strings in the crash dialig for:
1) the explanation that a user has crashed
and 2) the opt-in/send the crash info
and 3) the quit/restart buttons
are all part of the same string blob.
We should break these up in firefox 3.1 so we have the option for showing 1 and 3, or 1, 2, and 3 depending on if the user is in the 10% selected random pool of crash reporting users.
Comment 1•16 years ago
|
||
Particularly:
http://mxr.mozilla.org/mozilla/source/toolkit/locales/en-US/crashreporter/crashreporter.ini#12
CrashReporterDescriptionText2=%s had a problem and crashed.\n\nTo help us diagnose and fix the problem, you can send us a crash report.
We should split that into two strings, although I'm not sure of the l10n impact of trying to concatenate those two strings into something for display.
Reporter | ||
Comment 2•16 years ago
|
||
I'm pretty sure that shouldn't be a problem since there are really two distinctly different actions in those two sentences. Axel might have a better opinion on if this might cause problems.
Axel this bug is about still showing a post crash dialog to explain about the crash and to let users restart, but only letting some users see the additional part about submitting the crash so we can more effectively throttle crash reports on the client side. Any thoughts on the best way to do that for l10n?
Updated•16 years ago
|
OS: Mac OS X → All
Hardware: PC → All
Comment 3•16 years ago
|
||
I only see one reason that could break, and that is that someone has to ask for participation first, and then say that it is because the browser crashed.
I chatted with Gen over this, and Japanese is not affected. That doesn' really rule out that others could be effected, so I'd suggest to just go for a separate string. Something like CrashReporterNoSubmitDescriptionText or something. For most locales, that will just be a copy and paste, can you indicate that in a localization note?
Comment 4•16 years ago
|
||
We could do that, that'd be easy.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•