sway: Input are not correctly forwarded to XWayland windows

Hello,

I’m currently testing the 1.3 version, and I have found a what I think could be a bug : When a popup is spawned by a XWayland window and I close it, Sway refocus the window that spawned the popup. Unfortunately, the keyboard is not sending any input to the window even if sway is marking this window as being currently focused. I can reproduce this issue with several application on current release-candidate like vscode for instance.

Let me know if I can provide some details about this issue !

> swaymsg -t get_version
sway version 1.3-rc3

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 6
  • Comments: 21 (6 by maintainers)

Commits related to this issue

Most upvoted comments

I think I have the same issue.

  • Sway Version:

sway version 1.4

Debug Log:

sway.log

Configuration File:

Default

Reproduction:

What I did in the debug log:

  • Open terminal (Super+Enter)
  • $ firefox
  • Open Bookmark Overview (Ctrl+Shift+O)
  • Make sure mouse cursor is above the newly spawned window
  • Close Bookmark Overview (Ctrl+W).
  • No keyboard input is possible on Firefox until focus has been switched to another window.

Additional Information:

This happened with other XWayland windows as well.

It is neccessary to move the mouse onto the new window. Otherwise the main window will take input from the keyboard as usual when the second window is closed.

Edit: Be more specific that it is about the input from the keyboard.

I’m on Arch with wlroots 0.10.0-2 and sway 1.4-7 and this happens to me maybe 1 out of 20 times when opening a new tab in Firefox (using X11Wayland for it because native Wayland support was terrible last time I tried it.) The Firefox window is focused (blue title bar) with the cursor flashing in the address bar, but won’t accept input until I focus another window and switch back.

@ammgws I just tried it, it’s working now. Thank you 😃