[BUG] Wrong onPan events sequence

[lNikolayl]

Hi guys!

1. Describe the bug

Since the 10.1.0 version there is the issue with event sequence. Seems onPanStart event triggers after onPan. Not really sure that it's the expected behaviour.

2. IMPORTANT: Provide a CodeSandbox reproduction of the bug

Sandbox

Try to drag the white box and after that check the console logs.

3. Steps to reproduce

Steps to reproduce the behaviour:

1. Drag the white box (tap and move events)
2. Check the console logs

4. Expected behaviour

onPanStart event should be triggered first. (The "start" word semantically means before any others)

5. Video or screenshots

6. Environment details

Browser: Chrome 108.0.0.0

framer-motion 10.9.1
(the issue since 10.1.0)

[andreyfel]

@mattgperry do you know if there is a plan to fix this issue?

[andreyfel]

Still happening in 11.0.3

[andreyfel]

I think this commit is a root cause of this bug: d9d94e2#diff-ba855b96ec6081552117d1470f8681c63635736da63d6738ce907a2e6f1b33eaR34
onDragStart became an async event and onDrag is still sync. It makes onDrag to be called before onDragStart.

@mattgperry, what do you think what is the best way to fix it?