Text input is not functioning in Chromium and Electron with enabled Wayland mode when using Enigo.

[intbyte-100]

Description: Text input is not functioning in Chromium and Electron with enabled Wayland mode when using Enigo.

Environment:

• OS: Arch Linux
• Wayland Compositor: hyprland
• Enigo Version: 0.2.1
• Chromium Version: 128.0.6613.84
• Rust Version: 1.81.0

Steps to Reproduce:

1. Run a Wayland session.
2. Launch Chromium with enabled wayland ozon mode.
3. Execute the Enigo script to simulate text input.

Expected Behavior: Text input should be registered in the Chromium and Electron applications.

Actual Behavior: Text input does not appear in either Chromium or Electron applications.

Additional Information: Other applications are working correctly with Enigo in the same Wayland session.

[pentamassiv]

I don't have an idea why it would fail only for these applications. I don't use hyprland so I will likely not be able to test this for a few weeks/months. I think it is a bug on the compositor's side. If it works for other applications, enigo seems to work fine. Unless for the other applications X11 was used. Try to run the keyboard example with:

cargo run --example keyboard --no-default-features --features wayland

and test the other applications again. Even if the Wayland features is selected, X11 will not get deactivated, because some programs will still need it. If you disable the default features as well, enigo is built without any X11 support.