Consider changing the default scroll snap proximity threshold
Categories
(Core :: Layout: Scrolling and Overflow, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox118 | --- | fixed |
People
(Reporter: hiro, Assigned: hiro)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
We've been using 200px in CSS units for a while.
A wpt is supposed to work with the values in between 2px and 110px.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
It looks like the Chrome's threshold isn't a fixed value, it's 1/3 of scrollport?
Assignee | ||
Comment 2•2 years ago
|
||
And it looks like Webkit threshold isn't a fixed value, it's 0.3 of the scrollport.
Assignee | ||
Comment 3•2 years ago
|
||
Now the threshold is 0.3*snapport size
, it's mostly same as WebKit [1].
A difference is WebKit's threshold is based on the scrollport size. Given that
if scroll-padding
was specified due to a position: fixed
element or some
such, using snapport size (i.e. offsetted by the scroll-padding) is more
reasonable than using scrollport size.
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Backed out for causing mochitest failures in helper_scroll_snap_resnap_after_async_scroll.html
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | gfx/layers/apz/test/mochitest/test_group_scroll_snap.html | helper_scroll_snap_resnap_after_async_scroll.html | snap to 200px - got 468, expected 200
Assignee | ||
Comment 6•2 years ago
|
||
I was misunderstanding that this scrollDelta value for promiseMoveMouseAndScrollWheelOver
means that promiseMoveMouseAndScrollWheelOver
scrolls the given delta, but it's just used for creating OS internal events so it's hard to predict how far promiseMoveMouseAndScrollWheelOver
scrolls to.
I did tweak the scroll delta depending on platforms to make the test pass on all desktop platforms and android.
Comment 8•2 years ago
|
||
bugherder |
Description
•