Closed Bug 1421644 Opened 7 years ago Closed 7 years ago

Slow flinging on Android

Categories

(Core :: Panning and Zooming, defect, P3)

All
Android
defect

Tracking

()

RESOLVED DUPLICATE of bug 1448439
Tracking Status
firefox-esr52 --- wontfix
firefox-esr60 --- wontfix
firefox59 --- wontfix
firefox60 --- wontfix
firefox61 --- affected

People

(Reporter: snorp, Assigned: Carol)

References

Details

(Keywords: parity-chrome, Whiteboard: [gfx-noted][geckoview:klar])

We've had several users complain about the fling velocity being too low on Android. We should take a look at this and see what can be done. We do apply the APZ fling curve function to the initial fling velocity, so it appears we may already have the right knobs in place.
Do we have android-specific UX people that can take a look at tweaking this?
OS: Unspecified → Android
Priority: -- → P3
Hardware: Unspecified → All
Whiteboard: [gfx-noted]
Anthony, Carol, do you want to take a look at this?
Flags: needinfo?(chuang)
Flags: needinfo?(alam)
I think Carol should take the lead here. Will talk to her about it on Slack but clearing my NI for now.
Flags: needinfo?(alam)
Assigning to Carol per comment 3, so I can drop the needinfo and get this out of the triage queue.
Assignee: nobody → chuang
Flags: needinfo?(chuang)
I am tagging some Fennec bugs related to Chrome scrolling parity.
Keywords: parity-chrome
Whiteboard: [gfx-noted] → [gfx-noted][geckoview:klar]
Depends on: 1448439
I think this bug is a duplicate of bug 1448439 ("Copy Chrome's fling physics"), which Botond is fixing.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.