Preferences/Options longer dropdowns can be scrolled only by hovering over them
Categories
(Core :: XUL, defect, P5)
Tracking
()
People
(Reporter: csasca, Unassigned)
Details
Attachments
(1 file)
4.93 MB,
video/quicktime
|
Details |
Affected versions
- Firefox 68.4.1esr
- Firefox 72.0.1
- Firefox 73.0b6
- Firefox 74.0a1
Affected platforms
- Windows 10 & 7
- macOS 10.15
- Ubuntu 18
Steps to reproduce
- Launch Firefox
- Open Preferences/Options
- Go to Language and Appearance and access the Default font's dropdown list
- Hover over the upper and lower part of the dropdown
Expected result
- Nothing happens
Actual result
- The list scrolls only by hovering over.
Regression range
- I will see for a regression range.
Additional notes
- The actual issue can be seen in the attachment.
- On ubuntu, the issue is partially reproducible as the scroll only moves a little up or down, but going through the list is not possible only by hover as on macOS and Windows.
- Other longer dropdowns are affected as well.
Reporter | ||
Updated•4 years ago
|
Comment 1•4 years ago
|
||
Not sure if this one is a regression - I went back as far as 53 and could reproduce it.
Reporter | ||
Comment 2•4 years ago
|
||
Indeed this doesn't seem to be a regression. Reproduces way back on 29.0a1 too. Thanks mpj for looking into it.
Updated•4 years ago
|
Comment 3•4 years ago
|
||
The priority flag is not set for this bug.
:dholbert, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 4•4 years ago
•
|
||
I believe what's happening here is that there's a partially-visible list menu item, and when you hover the extreme visible top/bottom edge, you end up hovering that partially-visible menu item, and it snaps into view so that you can see what you're hovering.
I can reproduce this in XUL dropdown widgets (i.e. in about:preferences
as described here), but not in web-exposed HTML content dropdown widgets -- i.e. not with this testcase:
data:text/html,<select><option>a</option><option>b</option><option>c</option><option>d</option><option>e</option><option>f</option><option>g</option><option>h</option><option>a</option><option>b</option><option>c</option><option>d</option><option>e</option><option>f</option><option>g</option><option>h</option><option>a</option><option>b</option><option>c</option><option>d</option><option>e</option><option>f</option><option>g</option><option>h</option><option>a</option><option>b</option><option>c</option><option>d</option><option>e</option><option>f</option><option>g</option><option>h</option><option>a</option><option>b</option><option>c</option><option>d</option><option>e</option><option>f</option><option>g</option><option>h</option><option>a</option><option>b</option><option>c</option><option>d</option><option>e</option><option>f</option><option>g</option><option>h</option><option>a</option><option>b</option><option>c</option><option>d</option><option>e</option><option>f</option><option>g</option><option>h</option><option>a</option><option>b</option><option>c</option><option>d</option><option>e</option><option>f</option><option>g</option><option>h</option>
So this is a XUL-formcontrol-specific issue, as far as I can tell, and probably not something that's likely to be fixed, given that it's always behaved this way & we're actively trying to migrate off of XUL & onto HTML&CSS for all of our frontend code.
Comment 5•4 years ago
|
||
The priority flag is not set for this bug.
:bgrins, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Updated•1 year ago
|
Description
•