Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bindsym --release is not masked by LMB/RMB+mod floating_modifier #8162

Open
jlo62 opened this issue May 17, 2024 · 2 comments
Open

bindsym --release is not masked by LMB/RMB+mod floating_modifier #8162

jlo62 opened this issue May 17, 2024 · 2 comments
Labels
bug Not working as intended

Comments

@jlo62
Copy link

jlo62 commented May 17, 2024

  • Sway Version: swayfx version 0.4 (based on sway 1.9.0)

  • Debug Log: http://0x0.st/XPbJ.txt

  • Configuration File:

bindsym --no-repeat --release Super_L exec sirula

# Drag floating windows: Mod4 + leftmouse
floating_modifier Mod4 normal
  • Description:

bindsym --no-repeat --release Super_L exec sirula will start sirula like windows does. It will be masked when a other keybind is pressed. (see #8148 (closed) for info).
However, this will not be masked by moving/resizing windows with LMB/RMB + $mod. This cause my launcher to start every time after I move a window around (This is similar to #7863 (closed) ).

@jlo62 jlo62 added the bug Not working as intended label May 17, 2024
@emersion
Copy link
Member

Hm, we probably want to check for floating_modifier in handle_key_event() (maybe it would make sense to put in keyboard_execute_compositor_binding()?).

@emersion
Copy link
Member

BTW, how does i3 behave in this situation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Not working as intended
Development

No branches or pull requests

2 participants