When a client application with two or more top level widgets is run in a Wayland compositor the gesture events are not delivered to the correct top level widget.

QGestureManager::deliverEvents() uses the gesture's hotspot to find the top-level widget. It looks like the Wayland windows contain the same coordinates, so it is picking what it thinks is the top-level widget. If the QGestureManager::deliverEvents() is forced to use the gesture's context from m_gestureOwners, instead of the hotspot, the gesture is sent to the correct window.

To reproduce, please run the attached example which consists of the compositor and the client. Use mouse and touch screen to click the both top level widgets.

The QApplication::topLevelAt() with the global mouse event position for mousePressEvent() logging always shows "topLevelAtWidget=Right" even when clicking on the "Left" widget. When tapped with a touch screen the tap gesture is always showing "objectName=Right".