pixabay.com - Filtering option buttons are broken
Categories
(Web Compatibility :: Site Reports, defect, P1)
Tracking
(Not tracked)
People
(Reporter: rbucata, Assigned: emilio)
References
()
Details
User Story
platform:android impact:workflow-broken configuration:general affects:all
Attachments
(4 files)
Environment:
Operating system: Android 11
Firefox version: Firefox Mobile 128.0/126.0
Steps to reproduce:
- Navigate to: https://pixabay.com/ro/videos/search/ufo/
- Go to "Filters" and select any desired option
- Tap on the option and observe
Expected Behavior:
The option is selected
Actual Behavior:
A dot is present
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in Firefox Nightly, Firefox Release
- Does not reproduce in Chrome
Created from https://github.com/webcompat/web-bugs/issues/137674
Reporter | ||
Comment 1•5 months ago
|
||
Updated•5 months ago
|
Comment 2•5 months ago
|
||
Easily reproduced in responsive design mode on desktop. I'm not the right person to look into site JS.... @dholbert maybe?
Comment 3•5 months ago
|
||
Comment 4•5 months ago
|
||
Comment 5•5 months ago
|
||
Comment 6•5 months ago
•
|
||
The page is placing an absolute-positioned input type="radio"
element wayyyy off to the side in a scrollable container (with right:9999px
), and they're giving it zero height and width, which Chrome honors but Firefox does not (we floor the size to 4px).
Since we've got it as having a nonzero size, it actually contributes to the scrollable overflow for us, which means we would generate scrollbars if this element were overflow:auto
(in fact it's overflow:hidden
, but we effectively generate logical/invisible scrollbars to let it be programmatically scrolled-to). And when it becomes checked, we scroll to show it -- it's the tiny dot that was mentioned in comment 0 actual-results).
In comparison: in Chrome, the zero-sized radio button is actually zero-sized and hence doesn't contribute scrollable overflow, and hence it can't be scrolled to when its label is clicked.
If I open Chrome devtools to force width:4px; height:4px
on the radio button (to match Firefox's lower bound), then Chrome matches Firefox exactly on this site.
Comment 7•5 months ago
|
||
I filed bug 1903191 for the underlying platform difference here.
In the meantime, we could theoretically ship an intervention here. We could add appearance:none
to their hidden-radio-button styles[1], which makes Firefox actually render the radio button as zero sized, which prevents the issue here and makes us behave just like Chrome here:
[1] specifically, we want to add appearance:none
to this .hiddenInput--Rzalk
rule:
.base--CeYsk > .input--b6Wi1 .hiddenInput--Rzalk {
position: absolute;
right: 9999px;
width: 0;
height: 0;
https://pixabay.com/static/frontend/client.ea46d9d65428317a1d14.css
Assignee | ||
Comment 8•5 months ago
|
||
Fixed by bug 1903191 I guess?
Assignee | ||
Updated•5 months ago
|
Comment 9•5 months ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #8)
Fixed by bug 1903191 I guess?
Yup, seems to be. I just retested and confirmed that the issue no longer reproduces. (For completeness: there is one minor glitch when you tap on a filter option [only the first time you tap any option, I think] where the filter category auto-closes instead of activating the option, but I recall that happening on Chrome as well.)
Thanks!
Updated•5 months ago
|
Description
•