Items "Regular" "Bigger" "Smaller" in Size choice dropdown menu are cropped

RESOLVED FIXED

Status

Thunderbird
Preferences
--
trivial
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: Jean-Bernard Marcon, Assigned: Jean-Bernard Marcon)

Tracking

({polish, ux-control})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(4 attachments, 1 obsolete attachment)

(Assignee)

Description

6 years ago
User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0b10pre) Gecko/20110114 Firefox/4.0b10pre
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b8pre) Gecko/20101116 Thunderbird/3.3a1

Items in the dropdown menu for Size of the texte choice are not completely readable unless you click to see the whole list

Reproducible: Always

Steps to Reproduce:
1. Goto Edit>Preferences>Display tab
2. The plain Texte Messages zone offers a Size choice
 Words are not completely visible
Actual Results:  
 Words are not completely visible

Expected Results:  
It would be better to have the default choice at least learly visible without clicking

Please note that I have no such visual issue on Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
(Assignee)

Comment 1

6 years ago
target file for modification is /content/messenger/preferences/dispaly.xul
(Assignee)

Comment 2

6 years ago
Created attachment 504115 [details] [diff] [review]
small patch to restore full visibility
(Assignee)

Comment 3

6 years ago
Created attachment 504116 [details]
visual problem before
(Assignee)

Comment 4

6 years ago
Created attachment 504117 [details]
correct layout after patch
Assignee: nobody → GoofyFr
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Keywords: polish, ux-control
Attachment #504115 - Flags: review?(bwinton)
(Assignee)

Comment 5

6 years ago
mmmh btw I realize the same little addition sizetopopup="always" should be applied in the same file for the Font size dropdown list which numbers are completely unvisible (to be seen on my attached screenshots)
(In reply to comment #5)
> mmmh btw I realize the same little addition sizetopopup="always" should be
> applied in the same file for the Font size dropdown list which numbers are
> completely unvisible (to be seen on my attached screenshots)

Bigger patch please ?
(Assignee)

Comment 7

6 years ago
Created attachment 504182 [details] [diff] [review]
tested tiny patch

a bigger patch including a second similar correction
Attachment #504115 - Attachment is obsolete: true
Attachment #504115 - Flags: review?(bwinton)
Attachment #504182 - Flags: review?(bwinton)
Attachment #504182 - Flags: ui-review?(clarkbw)
Attachment #504182 - Flags: ui-review?(clarkbw) → ui-review?(nisses.mail)
There seems to be a small error in the patch in that it tries to apply to home/famille/Bureau/truncationOnItems/after/display.xul a user I don't have on my system :)
Comment on attachment 504182 [details] [diff] [review]
tested tiny patch

But judging from the screenshot, I think it would be good to use the same spacing in both boxes, as it would look a bit better, so some spacing in the Size dropdown would be good.
Attachment #504182 - Flags: ui-review?(nisses.mail) → ui-review-
Comment on attachment 504182 [details] [diff] [review]
tested tiny patch

(I'm clearing out my review request, cause it didn't get the ui-r, but I basically agree with what Andreas said.)
Attachment #504182 - Flags: review?(bwinton)
Could the cause just be that the dialog isn't wide enough on Linux? On Mac I don't see an issue.

From what I can tell the button should size to the drop-down by default, unless there's not enough room available for the button...

Comment 12

4 years ago
Created attachment 692539 [details]
Screenshot showing no artifact

There is no artifact while looking at this tab on latest build. Notice that dialog box has been resized to its minimum possible in order to show if menu-lists showed those "...", but it didn't happen.

The same occurs when opening the dialog box without resizing it.

This bug hasn't revieved any activity from its assignee since a year or so ago.

So, I mark it as FIXED, as long as when reported was a correct bug.

Updated

4 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.