Created attachment 832671 [details] MMI When the user inputs an MMI code or the MMI Call Barring code in the Dialer app, the respective title header is truncated. Repro Steps: 1) Updated Buri to BuildID: 20131114004004 2) Select Spanish as the language. 3) Open the Dialer app. 4) Input *#30# and press the green call button. 5) Verify the title header is truncated. 6) Repeat steps 4 and 5 for *33*XXXX# (XXXX = any four digit number). Actual: The title headers are truncated. Expected: The title headers would be fully displayed. Environmental Variables: Device: Buri v1.2 Mozilla RIL BuildID: 20131114004004 Gaia: 3e67ddf7d2680d1ef01441641f4ca2e0e4006887 Gecko: 948e30162eac Version: 26.0 Firmware Version: 20131104 Repro frequency: 100% See attached: Screenshots
We could truncate it this way: - "ID de llamada entrante" -> "ID llamada entrante" - "Bloqueo de llamadas" -> "Bloqueo llamada" But, IMO, the first one won't fit and can't be further shortened.
Agree with Ricardo, changing, even if the first one is too long.
Issue is reoccurring in latest 1.2 build. Attaching new screenshot and reopening. Screenshot: 2013-11-27-14-50-32.png Environmental Variables Device: Buri v1.2 COM RIL Build ID: 20131127004001 Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/14e91ab12441 Gaia: 92cd11ea023dd6598d82d859ae3c945ff6589ce6 Platform Version: 26.0 RIL Version: 01.02.00.019.102 Firmware Version: V1.2_US_20131115
(In reply to Roland Kunkel [:RolandK] from comment #5) > Created attachment 8339568 [details] > 2013-11-27-14-50-32.png As said in comment #2, we cannot shorten that string anymore.
Therefore adding UX team for some help
Flagging Eric for another manual adjustment.
Created attachment 8350058 [details] screen.png Let's try a manual fix by moving the div line and "Enviar" closer to the right side. The div line should be 4.8 rem from the right with "Eviar" centered.
Humm... Inma, Willy, can you check if this bug is still valid in 1.4/2.0?
(In reply to Ricardo Palomares from comment #10) > Humm... Inma, Willy, can you check if this bug is still valid in 1.4/2.0? Sorry I couldn't get back to you sooner. Just updated my device to the latest build, and followed the above steps to reproduce the bug. We can mark this bug as "Fixed" :)
3 years ago