Touch input silently drops on_press after a mouse is used on Wayland

Is your issue REALLY a bug?

• My issue is indeed a bug!
• I am not crazy! I will not fill out this form just to ask a question or request a feature. Pinky promise.

Is there an existing issue for this?

• I have searched the existing issues.

Is this issue related to iced?

• My hardware is compatible and my graphics drivers are up-to-date.

What happened?

I have a touchscreen and a mouse connected at the same time, on Wayland (sway). Touch works well until I move the mouse. After I move the mouse one time, tapping a button does not work anymore. The button still shows a hover color when I tap it, but on_press does not fire. If I then move the mouse cursor onto the same button, the tap works again.

Steps to reproduce:

1. Run an iced app on a Wayland compositor (I used sway), with a touchscreen and a mouse on the same seat.
2. Move the mouse once, so the pointer is on the window.
3. Tap a button on the touchscreen.
4. The button shows its hover color, but on_press does not fire.
5. Move the mouse cursor to the same button. Tap again. Now it works.

SSCCE: this is just the counter example from examples/ in this repo, ran at fullscreen using iced::application instead of iced::run without feature flags.

Environment:

• OS: Debian trixie, ARM (Cortex-A53)
• GPU: Mali-400 via the lima driver (no Vulkan on this hardware)
• Compositor: sway
• Touch device: Weida Hi-Tech CoolTouch System

What is the expected behavior?

A touch press should be tested against the position of that touch. Tapping a button on the touchscreen should fire on_press every time, and it should not matter where the mouse is or when the mouse last moved.

Version

crates.io release

Operating System

Linux

Do you have any log output?

There is no error, no panic and no warning from iced. The tap is simply ignored, so there is nothing in the output to show.