OK, the first bug 1481570 has a fix up for review. That's faulty end-of-multifinger gesture detection. Probably doesn't apply to Unity, just the Mir demo server..
The second bug (the Mir part of this one) seems to be a simple matter of faulty end-of-gesture detection introduced in r2652. The exact problem seems to be the new SurfaceInputDispatcher::dispatch_touch gesture_owner logic that was introduced. It assumes there's no shell that might consume your touch events in handling app-switching gestures. If the shell does correctly consume those touch events that triggered the app switch then the gesture_owner logic introduced in r2652 doesn't work and it keeps delivering touches to the old window (which is now hidden) instead of the new one.
So that needs fixing in Mir. But it doesn't mean there aren't additional timing bugs in other components after that... :/
OK, the first bug 1481570 has a fix up for review. That's faulty end-of-multifinger gesture detection. Probably doesn't apply to Unity, just the Mir demo server..
The second bug (the Mir part of this one) seems to be a simple matter of faulty end-of-gesture detection introduced in r2652. The exact problem seems to be the new SurfaceInputDis patcher: :dispatch_ touch gesture_owner logic that was introduced. It assumes there's no shell that might consume your touch events in handling app-switching gestures. If the shell does correctly consume those touch events that triggered the app switch then the gesture_owner logic introduced in r2652 doesn't work and it keeps delivering touches to the old window (which is now hidden) instead of the new one.
So that needs fixing in Mir. But it doesn't mean there aren't additional timing bugs in other components after that... :/