Comment 13 for bug 1531517

dandrader:
It's been a useful quirk of Android input until now that multi-touch gestures get separate events for each finger, but I think we all need to ensure our client code does not assume that's always true.

It wasn't a design choice of Mir's, but just something we inherited from Android. There's a good argument that Mir's semantics should not change, because it annoys people obviously. On the other hand it would be difficult to keep all the quirks of Android input in the transition to libinput. And I think the semantics of receiving a single event where two fingers go down at once is perfectly valid. We should all be writing client code that expects that might happen.