Description: The string "Current passcode" is truncated in the header under the phone lock settings. Repro Steps: 1) Updated Buri to Build ID: 20131024004000 2) Tap on "Settings". 3) Tap on "Phone lock". 4) Tap on "Passcode Lock" and create a passcode. 5) Tap on "Change Passcode". Actual: The string "Current passcode" appears truncated in the header. Expected: The string do not appear truncated. Environmental Variables Device: Buri v 1.2.0 COM RIL Build ID: 20131024004000 Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/ed279034d066 Gaia: c57951d06f6c9fa5a762d151e4c75214b988679f Platform Version: 26.0a2 RIL Version: 01.02.00.019.082 Notes: Repro frequency: 100% See attached: screenshot

Needs general UX solution (smaller font).

Thanks Ton. For similar issues please put UX team in "need more information": firefoxos-ux-bugzilla@mozilla.com thanks

Same as the other header issues; updated bugs accordingly. Flagging Eric to see if we want to address this ad hoc or wait for the header fix. Don't think this is egregious enough to block.

Hi, if we changed the sting to "Enter passcode" will it fit? I think it will be obvious to the user that this means the current passcode. If not we'll have to mark as dependent on bug 908300 and wait for a solution for the reduction of font size. Thanks!

Well, ‘enter passcode’ in English may look short, but would become ‘Voer wachtwoordcode in’ for Dutch, which will probably also be too long to fit the header (compare ‘Enter’ to ‘put in’ in imperative mood). Nevertheless, I could live with ‘Huidige code’ (=Current code) for 1.2 and 1.3, as it will be clear it’s the passcode that has to be entered.

(In reply to Ton from comment #5) > Well, ‘enter passcode’ in English may look short, but would become ‘Voer > wachtwoordcode in’ for Dutch, which will probably also be too long to fit > the header (compare ‘Enter’ to ‘put in’ in imperative mood). Nevertheless, I > could live with ‘Huidige code’ (=Current code) for 1.2 and 1.3, as it will > be clear it’s the passcode that has to be entered. Sounds good, thanks Ton!

Should be ‘fixed’ now.

verified on build 20140325004509 1.3.0.0-prerelease