Jump during inertial scroll with hold gesture in horizontally scrollable blocks
Categories
(Core :: Panning and Zooming, defect, P3)
Tracking
()
People
(Reporter: bano.notit, Unassigned)
Details
Firefox for Android
Steps to reproduce:
- Visit a long page with some horizontal blocks (e.g. https://ziglang.org/ru/learn/overview/)
- Initiate vertical inertial scroll (e.g. scroll down down)
- Tap and hold on first horizontally for like .5s
- Move finger in direction different from inertial scroll
Actual results:
The screen jumped for like 10% of viewport.
Expected results:
It should just scroll for the amount you move your finger in the last step.
Reporter | ||
Comment 1•1 year ago
|
||
Additional information:
You can initiate inertial scroll in horizontally scrollable block and hold-stop it outside of said block. It'll still jump on finger movement.
Comment 2•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Panning and Zooming' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 3•1 year ago
|
||
The severity field is not set for this bug.
:botond, could you have a look please?
For more information, please visit BugBot documentation.
Comment 4•1 year ago
|
||
Thanks for the report.
I've played around with the page in Firefox for Android for a few minutes, but I haven't been able to trigger the described jump. Most likely I'm just doing something slightly different than you. Any chance you could share a screen recording demonstrating the issue? (For bonus points, enable "Show pointer location" in Android's Developer Options, which shows more clearly how you're interacting with the page during the screen recording.) Thanks!
Reporter | ||
Comment 5•1 year ago
|
||
There are several failed attempts and I could not replicate it consistently, but in this video after 23s you can see sudden viewport jumps while touch did a small change.
Comment 6•11 months ago
|
||
Thanks for the video. I do see the jump at 23s, though I have not been able to trigger it myself so far.
Given the relatively infrequent nature of the issue, I'm going to assign this a severity of 3 for now.
Description
•