Closed Bug 1056932 Opened 10 years ago Closed 8 years ago

Proper handling of PANGESTURE_PAN events that are not surrounded by START and END events

Categories

(Core :: Panning and Zooming, defect)

Product:
Core
Component:
Panning and Zooming
Platform:
All
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: botond, Unassigned)

References

Details

(Whiteboard: gfx-noted) 

It seems that some devices send PANGESTURE_PAN events that are not surrounded by PANGESTURE_START and PANGESTURE_END events.

Currently, APZ does not handle this properly. We build the overscroll handoff chain on START and clear it on END, and call DispatchScroll() with the handoff chain in PAN, which is a no-op if the chain is not built.

We discovered this when bug 1039992 accidentally changed the behaviour from ignoring PAN events while the chain is not built, to crashing on them (bug 1056617 restores the 'ignoring' behaviour).
OS: Gonk (Firefox OS) → Mac OS X
Hardware: ARM → All
I think this is fixed now, in bug 1229039 I added some code to InputQueue::ReceivePanGestureInput that creates a new block for non-START pan inputs.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Whiteboard: gfx-noted
You need to log in before you can comment on or make changes to this bug.