Closed Bug 919625 Opened 11 years ago Closed 11 years ago

[browser] kinetic panning is broken if the user starts a scroll on a scrollable element

Categories

(Core :: Panning and Zooming, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: julienw, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #867787 +++ STR: * go to http://fr.m.wikipedia.org/wiki/Montbrison_%28Loire%29 * scroll down until "Localisation" * try to scroll again (up or down) when the first touch is on the map Expected: * the kinetic panning works (eg: the scroll continue after your touchend) Actual: * the kinetic panning does not work if the touchstart is inside the map.
This bug inherited koi+ from bug 867787 from whence it was cloned, but I think this bug is much less severe than the original thing (which is mostly fixed now) and so I don't think this needs to be koi+. Nom'ing for re-evaluation.
blocking-b2g: koi+ → koi?
Yep, I agree, sorry for this mess. Let's move this to FxOS 1.3, no need to risk uplifting an untested patch.
blocking-b2g: koi? → 1.3?
Summary: [browser] can't scroll up/down if the user starts a scroll left/right on a scrollable element → [browser] kinetic panning is broken if the user starts a scroll on a scrollable element
This is working for me with APZC on? Julien, is it still a problem with it off?
I'm testing this in the browser, which, I think, always has APZC? I still see the problem with either "APZC for apps" enabled or disabled, on the exact same STR :)
Push out to 1.4
blocking-b2g: 1.3? → 1.4?
Component: Graphics: Layers → Panning and Zooming
blocking-b2g: 1.4? → ---
Now that bug 965871 is fixed, this should no longer happen. qawanted to confirm.
Keywords: qawanted
I retested and this has been fixed.
Status: NEW → RESOLVED
Closed: 11 years ago
Keywords: qawanted
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.