Closed Bug 816243 Opened 13 years ago Closed 13 years ago

Overlay long text does not fit correctly for the tabs in the awesome screen

Categories

(Firefox OS Graveyard :: Gaia::Browser, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:+)

VERIFIED FIXED
B2G C4 (2jan on)
blocking-basecamp +

People

(Reporter: nhirata, Assigned: Margaret)

Details

(Whiteboard: l10n, visual design, interaction design)

Attachments

(3 files)

Attached image screenshot
## Environment : Unagi phone, build 2012/11/27 ## Repro : 1. go to settings -> languages and set to french 2. hit home 3. launch browser 4. tap into the url bar or add a new tab ## Expected : 1. The title of the tabs fit correctly ## Actual : 1. the history tab is on a line by itself. ## Note : 1. happens on unagi and otoro 2. noming in concern for spanish/portugese
The combination of the horizontal tab interaction design and curved tab visual design probably makes it impossible to solve this bug through clever translation alone. We definitely need to test this with Spanish/Portuguese or whatever our initial shipping languages are and I think we need UX mockups showing how it should be presented in these languages. It may be that this actually requires a design change like using icons instead of text in order to accommodate Latin languages on such a small screen.
Whiteboard: l10n → l10n, visual design, interaction design
Can you push the left and right tabs closer to the edge (potentially crop them) so all the text fits? Also are these the shortest labels / translations available?
Priority: -- → P1
Regardless of locale, this breaks the UI, which should not be possible. Tab text should be truncated *at worst*, and ideally the locale testing will change the text to fit into the available space. This is essentially a browser change. The local string changes should be in separate bugs for each locale.
blocking-basecamp: ? → +
Priority: P1 → P2
Summary: [Browser][l10n] French does not fit correctly for the tabs in the awesome page. → overly long text does not fit correctly for the tabs in the awesome screen
We ran into this same issue for Firefox for Android. In that case we decided to marquee the text (very Android), but I don't know if that's desired or even an easy option for B2G (see bug 753880).
Attached patch PatchSplinter Review
Let's truncate the text for now so the browser is not broken and hope localizers will find convenient strings.
Attachment #686881 - Flags: review?(ben)
Summary: overly long text does not fit correctly for the tabs in the awesome screen → Overlay long text does not fit correctly for the tabs in the awesome screen
Comment on attachment 686881 [details] [diff] [review] Patch This solution isn't perfect and it isn't as flexible as I would like, but it is an improvement on what we currently have so let's go with that for now.
Attachment #686881 - Flags: review?(ben) → review+
(In reply to Ben Francis [:benfrancis] from comment #7) > Comment on attachment 686881 [details] [diff] [review] > Patch > > This solution isn't perfect and it isn't as flexible as I would like, but it > is an improvement on what we currently have so let's go with that for now. You're 100% right. This solution is a shortcut. Something better would be desirable for v2 but that sounds ok to unblock the bug with such a hack right now. thanks!
The issue is still occurring in build 20130102070202 on Unagi.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: nobody → 21
Attached patch follow-up patchSplinter Review
Vivien, do you remember why you chose 37px for this? I upped the value, and that fixed the issue, but I really want to figure out what geometry is going into this calculation (I tried drawing it out, but I only managed to confuse myself). This issue is also reproducible if you run Gaia in desktop Firefox, so it's nice to use that for debugging the CSS. And, it's out of scope for v1 at this point, but shouldn't the tabs just each take up 1/3 of the space, instead of shifting to the left if the strings are short?
Attachment #697184 - Flags: review?(21)
Assignee: 21 → margaret.leibovic
The patch basically prevented each tab taking up more than a third of the width in order to prevent tabs dropping onto the next line. The side effect of this is that a tab can't take up more than a third of the space, even if more than a third of the space is available!
(In reply to Ben Francis [:benfrancis] PTO until 2nd January from comment #12) > The patch basically prevented each tab taking up more than a third of the > width in order to prevent tabs dropping onto the next line. The side effect > of this is that a tab can't take up more than a third of the space, even if > more than a third of the space is available! Yeah, I understand the logic, I was just confused by why calc(33% - 37px) magically equaled a third of the width :) And the last part of my comment was just an opinion that I feel like it would look nicer if each tab was just always a third of the width, such that the middle one was always be centered.
(In reply to Margaret Leibovic [:margaret] from comment #13) > Yeah, I understand the logic, I was just confused by why calc(33% - 37px) > magically equaled a third of the width :) Oh sorry, I assume that was what Vivien calculated as the maximum size could be to accommodate the curved tab design, but I don't know how he calculated it. Have you tested your patch on the device? Text sizes can be rendered differently in desktop Firefox. > And the last part of my comment was just an opinion that I feel like it > would look nicer if each tab was just always a third of the width, such that > the middle one was always be centered. That might look odd in landscape mode or on a larger device. I haven't yet figured out some CSS magic to use all the available space.
Comment on attachment 697184 [details] [diff] [review] follow-up patch I don't remember the logic. Was mostly by experimenting but that should be good enough for v1.
Attachment #697184 - Flags: review?(21) → review+
Target Milestone: --- → B2G C4 (2jan on)
(In reply to Ben Francis [:benfrancis] from comment #14) > Have you tested your patch on the device? Text sizes can be rendered > differently in desktop Firefox. Yeah, I tested on the unagi, and 39px worked. Maybe in the future we can do something with flexbox to make this more robust :) https://github.com/mozilla-b2g/gaia/commit/dc8ec3777431afdbe63c3460cea5ee6c3046c21f
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Verified on Unagi, Build Id:20130114073222
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: