Closed Bug 382128 Opened 17 years ago Closed 17 years ago

Fix crash reporter description for non-firefox apps

Categories

(Toolkit :: Crash Reporting, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: dcamp, Unassigned)

References

Details

The crash reporter description is too firefox-specific, should be specified by the XR app data.
Actually I would think that crashreporter.ini should be application (and locale) specific. At least that's what we do currently.
Well it's going to wind up in toolkit/locales. We could potentially add another file, like crashreporter-app.ini that had optional app-specific strings. I don't want to encode stuff into the main crashreporter.ini since we'd like to continue to build and ship it with XULRunner.
Looking at the strings, are they really too firefox specific? I'd rather say the opposite way around. Anyway. I'm tempted to say that we could just make browser overwrite the toolkit one at build time, but that seems to break for depend builds, at least I don't see a way to not break it. For a xulrunner application, how would crashreporter even find the application specified information? Can that be done? I really just don't know. I'd ask Benjamin, so I do.
(In reply to comment #3) > For a xulrunner application, how would crashreporter even find the application > specified information? Can that be done? I really just don't know. I'd ask > Benjamin, so I do. A xulrunner application could ship its own crashreporter.ini and stuff like the vendor and application name is already read from an extra file written from within the exception handler.
Turns out I'm going to fix this in bug 412989.
Depends on: 412989
The l10n changes I checked in effectively fix this, once bug 412989 gets fixed Firefox will have its special text back.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.