Sway: Drag-and-drop causes Firefox on Wayland to ignore keypresses

Created on 5 Mar 2019  路  6Comments  路  Source: swaywm/sway

  • Sway Version:
    sway version 1.0-rc1-144-ga6711740 (Mar 5 2019, branch 'master')

  • Debug Log:
    https://0x0.st/zo2t.log (firefox-wayland.log)
    https://0x0.st/zo2v.log (sway.log)

  • Configuration File:
    https://0x0.st/zo2y.txt (config)

  • Steps to Reproduce

  • Start Firefox
  • Go to a site where drag-and-drop is used, in example https://catbox.moe
  • Start Nautilus
  • Drag an image into Firefox.
  • Notice that typing has no effect anymore, like for example in the address bar.

It works again when changing to a different window and then back to Firefox.

bug inpukeyboard

Most helpful comment

This seems to be a general DND issue, it happens with any client. Just came across it with an app I'm developing and then tested dragging files between 2 nautilus windows and it always happens. The keyboard input just works after switching focus to another client and then getting it back to it.

This is the debug log for the nautilus test I describe above, hope it helps on further analysis.

All 6 comments

Not sure if this is related, but Alt+Left and Alt+Right doesn't work on Firefox on wayland either.

Can someone confirm this is specific to Firefox?

Because I have the problem with:

  • Firefox -> Firefox
  • Firefox -> Anki

Can someone confirm this is specific to Firefox?

No, it also happens with mpv for me (Thunar -> mpv). mpv just ignores everything from keyboard unless you refocus it (mouse works fine).

This seems to be a general DND issue, it happens with any client. Just came across it with an app I'm developing and then tested dragging files between 2 nautilus windows and it always happens. The keyboard input just works after switching focus to another client and then getting it back to it.

This is the debug log for the nautilus test I describe above, hope it helps on further analysis.

This seems to be fixed on Sway 1.5. I no longer have this issue

https://github.com/swaywm/sway/pull/5489 Seems to be the source of the fix. This can probably be closed.

Was this page helpful?
0 / 5 - 0 ratings