Closed Bug 931228 Opened 11 years ago Closed 11 years ago

[B2G][1.2][l10n][System] Nederlands: Text in the what's in a crash report page is cutoff at the bottom

Categories

(Mozilla Localizations :: nl / Dutch, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v1.2 affected)

RESOLVED FIXED
Tracking Status
b2g-v1.2 --- affected

People

(Reporter: KTucker, Unassigned)

References

Details

(Keywords: l12y, Whiteboard: LocRun1.2)

Attachments

(2 files)

Attached image 2013-10-24-17-45-16.png
Description:
Text in the "What's in a crash report?" page is cutoff at the bottom.

Repro Steps:
1)  Updated Buri to Build ID: 20131025004000
2)  Cause a crash to occur.
3)  Tap on "What's in a crash report?".
4)  Look at the bottom of the page.

Actual:
Text is cutoff at the bottom of the screen.

Expected:
All text is visible on the page.

Environmental Variables
Device: Buri v 1.2.0 COM RIL
Build ID: 20131025004000
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/5eabd267ef04
Gaia: 606517ceafe0950c2b89822d5f13353743334f2c
Platform Version: 26.0a2
RIL Version: 01.02.00.019.082 

Notes:
Repro frequency: 100%
See attached: screenshot
Asking for some UX help here
Blocks: 928174
Flags: needinfo?(firefoxos-ux-bugzilla)
Keywords: l12y
This should not be an issue, as most locales use longer text than English. Can’t reproduce, but don’t see real options to shorten the text, except for removing one word (‘wordt’) that might just make the last line fit. Note that we’re talking one line here with only one word for our locale, though it may depend on the device, and we would still be missing a little whiteroom at the bottom for a proper view in our case. Will remove that word above anyway though.

I’m not really into messing around to make words fit without 100% guarantee it will do everywhere. Also, I’m not sure whether the hypernation feature is about to be used here as well (hopefully not), or the same for auto spacing it could become worse by using that. I’d rather see the useless whiteroom used, or the entire font to be reduced, hence needing a UX solution allright.
Eric can advise on font adjustments. Flagged.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(epang)
This page should be scrollable so that the user can scroll up to read any text that doesn't fit on one screen.
Flags: needinfo?(epang)
Depends on: 868345
Seems no longer an issue now that the page is scrollable.
Thanks Ton. Please resolve fix in this case, next time you see the issue is resolved
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
The fix is landed on the master build, however the issue still appears on the latest 1.2 build

Device: Buri 1.2 COM
BuildID: 20140102004001
Gaia: b1bc88386c781148a25091bf2eeee3ba217281d0
Gecko: 0c11156c7d9b
Version: 26.0
RIL Version: 01.02.00.019.102
Firmware Version:v1.2_20131115

Device: Buri 1.4 Master build
BuildID: 20140102040201
Gaia: 67a82f88da231969efa4d22df9fb946abf2cf4df
Gecko: 540d85f60c57
Version: 29.0a1
Firmware Version: v1.2_20131115
Would you mind posting a new screenshot? I can't reproduce, at least not by killing the b2g process (the banner screen appears though). ‘Wordt’ in the last visible line should be gone now, and I also wonder about the spacing (‘ons privacybeleid’)
Attached image New screenshot
To see the crash report page you need to reset your device
Still couldn’t reproduce, but shortened the first paragraph and included a necessary space in http://hg.mozilla.org/releases/gaia-l10n/v1_2/nl/rev/6c3a58d90f0e. Please reevaluate after today’s/tomorrow’s build.
While you’re at it (and if it isn’t much trouble), could you please also check on master and en-US? The trailing end space (after ‘in our’) may be needed in any version and locale while it lacks in most cases.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: