Closed
Bug 928876
Opened 12 years ago
Closed 9 years ago
Inappropriate line break in tabzilla for some locales
Categories
(Websites :: Tabzilla, defect)
Websites
Tabzilla
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: joradan0, Assigned: kohei)
References
Details
(Whiteboard: [kb=1173918] )
Attachments
(3 files, 1 obsolete file)
Some localizations of the word 'Innovations' are too long, resulting in an inappropriate line break. The last character of the word ends up on a new line.
Affected locales:
da, de, es-MX, es-CL, es-AR. There might be more.
| Assignee | ||
Comment 1•12 years ago
|
||
I have thought the same thing. How about widening the columns like this?
| Reporter | ||
Comment 2•12 years ago
|
||
I like this solution. Widening all columns would probably solve similar problems with translations in the other columns.
| Assignee | ||
Comment 3•12 years ago
|
||
:pascalc feedback?
At least the line breaks should be avoided by using CSS text-overflow.
Flags: needinfo?(pascalc)
OS: Windows 7 → All
Hardware: x86_64 → All
Updated•11 years ago
|
Whiteboard: [kb=1173918]
| Assignee | ||
Updated•11 years ago
|
Component: Pages & Content → Tabzilla
Product: www.mozilla.org → Websites
Target Milestone: --- → 1.5
| Assignee | ||
Comment 4•11 years ago
|
||
Sorry for the bugspam -- the Target Milestore was set unexpectedly.
Target Milestone: 1.5 → ---
Comment 5•11 years ago
|
||
I like this new layout, it gives locales a lot more space for strings.
Updated•11 years ago
|
Flags: needinfo?(pascalc)
| Assignee | ||
Comment 6•11 years ago
|
||
pascalc: thanks, I'll send a PR!
Assignee: nobody → kohei.yoshino
Status: NEW → ASSIGNED
| Assignee | ||
Comment 7•11 years ago
|
||
| Assignee | ||
Comment 8•11 years ago
|
||
I have tested some locales and the new layout works fine.
Added a link to the home page to fix Bug 742598 too.
Note that the "Home" is not included in main.lang but in lightbeam.lang. We have to move the string manually.
| Assignee | ||
Comment 9•11 years ago
|
||
en-US, an and da. In the an locale, Developer Network and Website Directory are both broken into 2 lines, but still fit in the new layout.
Attachment #819688 -
Attachment is obsolete: true
Comment 10•11 years ago
|
||
Adding smartell for design feedback.
I've been wondering if we should drop the "HOME" link (which is not clear whether it's the Mozilla home page, or the home page of whatever page tabzilla is one). Instead, we could link the four column headings:
MOZILLA (mozilla.org)
PRODUCTS (mozilla.org/products)
INNOVATIONS (?)
GET INVOLVED (mozilla.org/contribute)
While we're at it, we should remove "PROJECTS" from the Mozilla column (it just redirects to /products, which already has a column/links). If we linked Get Involved to /contribute, we may also be able to eliminate the VOLUNTEER link.
These changes would reduce the max number of rows to 4.
Alternately, the WEBSITE DIRECTORY link could move under the MOZILLA column.
Sean?
Flags: needinfo?(smartell)
| Assignee | ||
Comment 11•11 years ago
|
||
The links in Tabzilla can be organized... in some way. WebFWD, Labs and Webmaker are actually on the Product page. Research is not there though. Support can be under Products? How about Add-ons and Marketplace? Developer (Network) can be under Get Involved? Hmm...
So I thought we could revisit those links later, and focus on the layout issue and the Home link this time.
| Assignee | ||
Comment 12•11 years ago
|
||
So the pull request has been closed. How can we fix this issue?
Comment 14•11 years ago
|
||
There's one more issue in the german edition (de). The word "ENTWICKLERNETZWERK" is too long for the column "MOZILLA", but I think that would be fixed with the planned changed. https://www.mozilla.org/de/
Comment 16•11 years ago
|
||
We had some good discussion around what Tabzilla Next would be at our last Engagement all-hands. Let me look into what timelines are like and if that's something we could ramp up to help with these issues.
Flags: needinfo?(smartell)
Comment 20•10 years ago
|
||
wow doesn't look like the issue still exists.
What's the current status?
What do you think about using a min-width and in every other case let the browser decide which width is possible for the current page's width. (so no width and no max-width)
Comment 21•10 years ago
|
||
ups ^^
I wanted to say:
looks like the issue still exists.
(I have edited the sentence during writing but didn't pay any attention to what I said before)
| Assignee | ||
Comment 22•10 years ago
|
||
Yes, this issue still exists unfortunately.
Since Tabzilla.next has been delayed, can we fix it with my proposal as a temporary solution? The screenshot is attached in my comment 9. Thoughts anyone?
| Assignee | ||
Comment 24•9 years ago
|
||
As you might know, Bug 1151579 has replaced Tabzilla with a static Mozilla tab. The old assets are still available, but no site is probably using it. Closing all Tabzilla-related open bugs at this moment.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•