Allow snap target elements, which were the targets on an axis, for the other axis when re-snapping
Categories
(Core :: Layout: Scrolling and Overflow, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox151 | --- | fixed |
People
(Reporter: hiro, Assigned: hiro)
References
Details
Attachments
(2 files)
We disallow such elements on re-snapping, but the spec doesn't mention it clearly. So we can be permissive for such elements.
| Assignee | ||
Comment 1•7 months ago
|
||
Updated•7 months ago
|
Backed out for causing mochitest related failures at browser_spinner_keynav.js
Backout link
Push with failures
Failure log(s)
| Assignee | ||
Comment 5•7 months ago
|
||
So the scroll container in the browser test is not horizontally scrollable. But while we are collecting snap targets on resnap, we do collect snap targets even if the scroller is not scrollable on the axis, thus with the check which was dropped in D285438, we did choose an in-appropriate snap target (which is the first element in tree order), that's because in the scroll container all children is positioned at 0 on X axis.
A patch is coming.
| Assignee | ||
Comment 6•7 months ago
|
||
Updated•6 months ago
|
Updated•6 months ago
|
Comment 8•6 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/8db4ba889629
https://hg.mozilla.org/mozilla-central/rev/cc8522a45c91
https://hg.mozilla.org/mozilla-central/rev/4bedc9077703
Updated•6 months ago
|
Description
•