Tracking all bugs filed concerning truncated text in various locales throughout the device, in order to see if a general UX solution can be found.
we've been noticing this issue of truncated words more and more with new shipping locales. I've discussed this with Bhavana, who has been talking about revisiting UX with UX team, which could eventually help out in resolving this issue. This is why I've added Stephany in CC as well as UX team in Need info.
blocking-b2g: --- → leo?
Adapting the title of this bug a bit, as it not only concerns truncated text, but also often text overlapping in certain areas. So this is more generally about the fact that there is not enough space on the screen.
Summary: [Meta][l12y] Text appears truncated for many locales throughout device → [Meta][l12y] Text very often appears truncated or overlaps, for many locales throughout device
Nominating as a blocker since all the bugs listed affect v1.1 shipping locales
Un-nominating. L10n team and UX team will get together and work on these issues
blocking-b2g: leo? → ---
No longer depends on: 893143
No longer depends on: 858175
UX has provided a suggested approach that we're going to try for these bugs. The short version of it is: if shortened copy and/or a center ellipsis will not work, and the only option is to adjust UI, please needinfo? email@example.com and we'll advise on the UI adjustment.
I think adjust UI (windows dimensions, fonts dimensions etc.) is solution for all these bugs. It is possible?
(In reply to Raul Malea from comment #6) > I think adjust UI (windows dimensions, fonts dimensions etc.) is solution > for all these bugs. It is possible? Potentially. Our l10n.js localization implementation, when it is directly localizing a DOM element (instead of just localizing a string when directly triggered via JS code) has the ability to set attributes on the DOM element. This includes the "style" attribute which would allow localizations to directly override the CSS that applies to a given string. Because the strings themselves are usually going to exist within some type of container element that will not be style-able via this method, the style directives that can be used may be strictly limited to messing with the font style, but in some cases padding and overflow may also be overridden. For a very specific example case in the e-mail app, see https://bugzilla.mozilla.org/show_bug.cgi?id=894696#c4 But basically the idea is that if you have: L10NID=Some String then you may also be able to do: L10NID.style=font-size: 1.2rem; padding: 0; or something appropriate like that. I'm not cc'ing myself on this bug because I am terrified of the dependency list resulting in never-ending bugspam. But feel free to send an e-mail to the dev-gaia list and I will be happy to respond there in the event anyone wants to discuss this mechanism further.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.