Closed
Bug 1722262
Opened 3 years ago
Closed 3 years ago
[Bug]: Uncontrolled/fast scrolling on zoom-in gesture on sites with zoom locked
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1685648
People
(Reporter: petru, Unassigned)
Details
From github: https://github.com/mozilla-mobile/fenix/issues/20501.
Steps to reproduce
- Open page when zoom-in gesture gesture is blocked - when try to zoom in by touching screen with two fingers and increase distance between these fingers the page does not zoom-in.
Exaple page: https://support.mozilla.org/pl/kb/nowosci-w-firefoksie-dla-androida?as=u&utm_source=inproduct&redirectslug=nowosci-w-aplikacji-firefox-dla-androida-w-wersji-79&redirectlocale=pl- Try to zoom in with two fingers placed vertically and increase distance between them.
2a. When only one of the fingers is released from screen then page position immediately jumps to the seconds finger that stiil touches screen. https://youtu.be/kULJ0rqfi2I?t=26
2b. When two fingers are released almost simultanuously then screen starts to scroll vertically very fast. The velocity is proportional to the distance made by fingers during zoom-in gesture. https://youtu.be/kULJ0rqfi2I?t=59Expected behaviour
When zoom-in is locked on page then zoom-in gesture should be ignored and page should not jumping or scrolling with uncontrolled manner.
Actual behaviour
After zoom-in gesture the page jumps or fast scrolls with uncontrolled manner on pages with zoom-in locked.
Device name
Xiaomi POCO X3 NFC 6/64GB M2007J20CG
Android version
Android 10
Firefox release type
Firefox
Firefox version
90.1.2 build #2015823035
Device logs
No response
Additional information
No response
Change performed by the Move to Bugzilla add-on.
Updated•3 years ago
|
Component: General → Panning and Zooming
Product: GeckoView → Core
Comment 1•3 years ago
|
||
Sounds like a dupe of bug 1685648?
Reporter | ||
Comment 2•3 years ago
|
||
Seems like it, thanks!
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•