Closed
Bug 546006
Opened 14 years ago
Closed 10 years ago
[Fx] Crashreporter dialog is too narrow for the text
Categories
(Mozilla Localizations :: de / German, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 528800
People
(Reporter: atopal, Unassigned)
Details
Attachments
(2 files)
The text in the crashreporter dialog is cut, because the dialog doesn't resize and the text doesn't break.
Reporter | ||
Updated•14 years ago
|
Assignee: nobody → a.topal
Status: NEW → ASSIGNED
Reporter | ||
Comment 1•14 years ago
|
||
Axel, is there a way to resize the crash reporter dialog? The size is okay for windows
Reporter | ||
Comment 2•14 years ago
|
||
Reporter | ||
Updated•14 years ago
|
Summary: Crashreporter dialog is too narrow for the text → [Fx] Crashreporter dialog is too narrow for the text
Reporter | ||
Comment 3•13 years ago
|
||
Hey Ted, can you comment?
Comment 4•13 years ago
|
||
We have code that's supposed to handle this, I'm not sure why it's not working: http://mxr.mozilla.org/mozilla-central/source/toolkit/crashreporter/client/crashreporter_osx.mm#435
Reporter | ||
Comment 5•13 years ago
|
||
Ted, can I assign this to you? It's assigned to me, but there is not much I can do as a localizer.
Comment 6•13 years ago
|
||
I don't think I have time to investigate this at the moment. :-/ Maybe you could rope someone with Win32 knowledge in to look at this?
Reporter | ||
Comment 7•13 years ago
|
||
Honestly, I wouldn't know whom to talk to. But as it sits here, no one will have a look at this. German is the second biggest locale after English, it's already embarrassing when Firefox crashes, but this broken window is doubly so. Ted, can you suggest anyone I should ping about this?
Comment 8•13 years ago
|
||
Oh, I'm sorry, this is on Mac. I asked on #macdev, but it's pretty sparse. I'm sorry, I don't have any other great ideas. :-(
Reporter | ||
Comment 9•13 years ago
|
||
Okay, thanks Ted. Axel, can you comment on what to do here?
Comment 10•13 years ago
|
||
So, I don't know either, the original patch is actually by Ted ;-) I dug a bit in, and found http://stackoverflow.com/questions/6692016/cocoa-animated-frame-in-preference-window, which says [window setFrame:windowFrame display:YES animate:YES]; whereas our code says [mWindow setFrame:windowFrame display: true animate: NO]; Reading cocoa docs, it seems that "YES" is bool, and "true" is not? CCing Josh who probably knows, I'm just stabbing at dust.
Comment 11•10 years ago
|
||
As far as I can see, the code hasn't been touched: http://mxr.mozilla.org/mozilla-central/source/toolkit/crashreporter/client/crashreporter_osx.mm#159 Josh, would altering it from [mWindow setFrame:frame display: true animate:NO]; to [mWindow setFrame:frame display:YES animate:NO]; fix the issue? See comment 10.
Assignee: a.topal → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(joshmoz)
Comment 12•10 years ago
|
||
That code is definitely not correct as written: https://developer.apple.com/library/mac/documentation/cocoa/reference/applicationkit/classes/NSWindow_Class/Reference/Reference.html I don't know if changing that will fix the bug or not, but it's worth a shot.
Comment 13•10 years ago
|
||
I think this is a dupe of bug 528800.
Comment 14•10 years ago
|
||
Definitely change the "true" to "YES". As to whether or not that will fix the bug I don't know, but I doubt it.
Flags: needinfo?(joshmoz)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•