When starting a scroll in a direction that isn't scrollable along the handoff chain, overscroll the innermost scrollable scroll frame
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox88 | --- | unaffected |
firefox89 | --- | wontfix |
firefox90 | --- | verified |
People
(Reporter: mstange, Assigned: hiro)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Steps to reproduce:
- Have a vertically scrollable <div> on a non-scrollable page. For example in the Slack or Matrix channel view.
- Scroll the div to the bottom, if it's not yet at the bottom.
- Initiate another scroll towards the bottom, inside the div.
Expected results:
The div should enter overscroll at the bottom.
Actual results:
Nothing happens.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Confirmed to be from bug 1705280. A simple test page is https://theres-waldo.github.io/mozilla-testcases/div.html.
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 4•4 years ago
|
||
This will be superseded by bug 1704080. That means that once after we allow overscrolling for non-scrollable containers, in this example case panning on the div will hand off to the root non scrollable container and then the root one starts overscrolling. Since bug 1704080 is marked as a blocker for overscroll-90, I am going to leave this for now.
Comment 5•4 years ago
|
||
Set release status flags based on info from the regressing bug 1705280
Comment 6•4 years ago
|
||
(In reply to Hiroyuki Ikezoe (:hiro) from comment #4)
This will be superseded by bug 1704080. That means that once after we allow overscrolling for non-scrollable containers, in this example case panning on the div will hand off to the root non scrollable container and then the root one starts overscrolling. Since bug 1704080 is marked as a blocker for overscroll-90, I am going to leave this for now.
Is that the desired behaviour, though? That, on a page like this (scrollable subframe + non-scrollable root), if the subframe is scrolled to the top, then scrolling upwards over the subframe overscroll the root and not the subframe?
ni?markus for thoughts on this
Reporter | ||
Comment 7•4 years ago
|
||
I would much prefer the rubber-banding in this case to happen on the nested scroll frame, not on the page. For example, on Matrix, I don't want the sidebar to bounce while the mouse is over the channel contents. Scrolling the innermost scroll frame will also be a more consistent experience if a user scrolls to the bottom with a series of multiple quick scroll gestures: every scroll gesture will scroll/overscroll the same scroll frame, even at the end when the scroll frame has already hit the edge.
Assignee | ||
Comment 8•4 years ago
|
||
Assignee | ||
Comment 9•4 years ago
|
||
I submitted a patch that it's the desired behavior I believe, i.e. overscroll handoff doesn't happen if the root content is not scrollable, it happens if the root content is scrolllable. I will write two gtests for this change, one is the root content is not scrollable either horizontally or vertically, the other is the root is only horizontally scrollable and verticall overscroll handoff doesn't happen.
Updated•4 years ago
|
Comment 11•4 years ago
|
||
Comment 12•4 years ago
|
||
bugherder |
Comment 13•4 years ago
•
|
||
Verified fixed on Firefox Nightly 90.0a1 (2021-05-11) (20210511093339) on iMac with OS 10.14.6 and MacBook Pro OS 11.2.3.
Still reproducible on Beta 89.0b10. Waiting for potential Uplift in Beta89 for further verification.
Comment 14•4 years ago
|
||
The patch landed in nightly and beta is affected.
:hiro, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 15•4 years ago
|
||
We've decided to not uplift this.
Comment 16•4 years ago
|
||
Marking this as Verified Fixed based on the last comment from Hiro.
Description
•