Closed
Bug 645588
Opened 14 years ago
Closed 13 years ago
German (de) strings are truncated
Categories
(Firefox for Android Graveyard :: General, defect, P3)
Tracking
(blocking2.0 -)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
blocking2.0 | --- | - |
People
(Reporter: tarend, Unassigned)
References
Details
Attachments
(1 file)
57.92 KB,
image/png
|
Details |
User Frederik N. reports:
"Antoher problem on my Atrix: Firefox seems to have a problem with the 960x540 resolution in the settings menu because all the toggle buttons on the right side are cut in the middle and so the user cannot see them (only if they are activated). Maybe you can fix this as well?"
Can we reproduce this issue?
We will not be taking this in a Firefox 4 update. If you disagree, please renominate it (blocking2.0:?) with justification why.
blocking2.0: ? → -
Comment 2•14 years ago
|
||
I don't see that on my atrix
Comment 3•14 years ago
|
||
Screenshot of the problem
Comment 4•14 years ago
|
||
I have uploaded a screenshot of the problem. It shows the whole screen, no editing from my side and it is also not possible to scroll to the right.
I have just tested if it is related to the German language and that seems to be the problem. When I switch to English everything looks like it should so you should edit the title of this bug report.
Comment 5•14 years ago
|
||
This is a locale string length problem. Shorter strings would work.
Comment 6•14 years ago
|
||
Can you rename and move this ticket to the language team or should I open a new ticket again for this with the correct problem?
Comment 7•14 years ago
|
||
Just a short answer would be enough to solve this ticket or move to the correct direction...
Updated•14 years ago
|
Summary: Firefox does not support 960x540 resolution on Atrix → German (de) strings are truncated
Comment 8•14 years ago
|
||
Just leave it here. Bug 658121 and bug 658099 are in the same component.
Comment 10•13 years ago
|
||
The bug is still present in Firefox mobile 8!
Comment 11•13 years ago
|
||
I've never seen this issue, it might be depended on your Android version. It displays correctly on my Nexus S with 2.3.3. In any case, this is moot since we are moving to native UI on mobile
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•