Incorrect positioning of <input type=range> slider on SoundCloud embed widget
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox115 | --- | unaffected |
firefox116 | --- | unaffected |
firefox117 | --- | verified |
firefox118 | --- | verified |
People
(Reporter: padenot, Assigned: emilio)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
STR:
- Open https://www.nts.live/shows/martha/episodes/martha-7th-july-2023
- Click the Play button
Expected:
- A widget appears at the bottom, the slider is positioned correctly at the center of the gutter
Actual:
- A widget appears at the bottom, the slider is not centered
Reporter | ||
Updated•1 year ago
|
Comment 1•1 year ago
|
||
Set release status flags based on info from the regressing bug 1735575
Comment 2•1 year ago
|
||
It looks like they're using ::-moz-range-thumb
/::-moz-range-track
as well as ::-webkit-slider-runnable-track
/::-webkit-slider-thumb
. If I drop the moz-prefixed CSS it seems to work. Emilio, could we easily ignore one set of prefixes if we see both?
Assignee | ||
Comment 3•1 year ago
|
||
It doesn't for me? What's causing the shift is the transform: translateY(-4px)
from the ::-webkit-slider-thumb
rule.
Assignee | ||
Comment 4•1 year ago
|
||
The layout of our slider is incompatible with Chrome's, as suspected in
bug 1735575 comment 9.
So this needs more re-think, maybe reworking the pseudo-element
structure when it's enabled. A potential path forward:
- Make these pseudo-elements proper pseudos (not just aliases).
- When this pref is enabled we don't even query the ::-moz- pseudos,
and read only ::-webkit-'s. - But we also don't generate the same tree structure, we generate
something more like WebKit's tree (thumb inside track inside
container), with this css1.
That would be somewhat sad because the whole situation of these pseudos
kinda sucks, see https://github.com/w3c/csswg-drafts/issues/4410.
Updated•1 year ago
|
Comment 5•1 year ago
|
||
Yeah, your assessment makes more sense, Emilio .
Comment 7•1 year ago
|
||
bugherder |
Updated•1 year ago
|
Reproducible on a 2023-07-12 Nightly build on macOS 12.
Verified as fixed on Firefox 117.0b5(build ID: 20230808215502) and Nightly 118.0a1(build ID: 20230809092330) on macOS 12, Windows 10, Ubuntu 22.
Description
•