Open
Bug 794004
Opened 13 years ago
Updated 3 years ago
The spaces between the icons of the home page are not the same
Categories
(Firefox :: General, enhancement)
Firefox
General
Tracking
()
UNCONFIRMED
People
(Reporter: vincent, Unassigned)
Details
(Whiteboard: [about-home][wontfix?])
Attachments
(1 file)
|
31.41 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120905151427
Steps to reproduce:
Go to about:home.
Actual results:
At the bottom of the page, icons are separated by spaces that are not of equal widths. The display seems a bit unbalanced.
Expected results:
Titles should perhaps have identical sizes ?
Comment 1•13 years ago
|
||
I believe this is due to the French translation that is longer than 74px.
Version: 15 Branch → Trunk
Can you please confirm if this happens with the latest en-US Nightly from nightly.mozilla.org? CCing Asa, the product manager for about:home. Asa have you seen an issue like this before?
Severity: normal → enhancement
Component: Untriaged → General
Comment 3•13 years ago
|
||
Yup confirmed on today's French nightly.
Comment 5•13 years ago
|
||
It's not showing this. That's because "Downloads" is shorter than "Téléchargements".
Comment 7•13 years ago
|
||
The buttons adapt to the text, that's the way we handled the l10n issue, making them same size there's concrete risk to overflow the page with some locale.
Updated•13 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [about-home]
Comment 8•13 years ago
|
||
I think it's a minor aesthetic issue and fixing it is non trivial, with risk of worse regression, my take on it is wontfix, but leaving the decision to Asa.
Whiteboard: [about-home] → [about-home][wontfix?]
Comment 9•13 years ago
|
||
Can't we have all buttons get the size of the largest button?
Comment 10•13 years ago
|
||
(In reply to Anthony Ricaud (:rik) [out between Sept 27 and Oct 1] from comment #9)
> Can't we have all buttons get the size of the largest button?
Though I think we could adjust this a couple of ways, there are far higher priority issues and so I wouldn't have us devote any of our regular core resources to this problem any time soon.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•