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

Keep floating window focused when moving it with keyboard #3543

siikamiika opened this Issue Dec 4, 2018 · 2 comments


None yet
4 participants

siikamiika commented Dec 4, 2018

I'm submitting a…

[ ] Bug
[x] Feature Request
[ ] Documentation Request
[ ] Other (Please describe in detail)

(maybe even bug/regression, can't remember past behavior)

Current Behavior

  1. open floating window
  2. move it with keyboard using move up|down|left|right <n>px
  3. mouse cursor leaves the floating window because the window has moved away from it (not because the mouse was moved), and the next thing under the mouse cursor is focused
  4. anything that happened to be under the cursor is now somewhere else

Desired Behavior

3. doesn't happen and the floating window that's being moved stays focused. Using focus_follows_mouse no in config would fix this issue, but I want to be able to focus with mouse when I move it myself.


Output of i3 --moreversion 2>&-:

i3 version: 
Binary i3 version:  4.16 (2018-11-04) © 2009 Michael Stapelberg and contributors
Running i3 version: 4.16 (2018-11-04) (pid 744)to abort…)
Loaded i3 config: /home/siikamiika/.i3/config (Last modified: Tue 04 Dec 2018 11:26:44 PM EET, 2346 seconds ago)

The i3 binary you just called: /usr/bin/i3
The i3 binary you are running: i3
- Linux Distribution & Version: Arch Linux, 4.19.2-arch1-1-ARCH
- Are you using a compositor (e.g., xcompmgr or compton): no

@i3bot i3bot added the enhancement label Dec 4, 2018

@Airblader Airblader added bug 4.16 and removed enhancement labels Dec 5, 2018


This comment has been minimized.


Airblader commented Dec 5, 2018

Retagging as a bug


This comment has been minimized.


xzfc commented Dec 5, 2018

This reproduces occasionally on 4.16.
I can't see the precondition now, but it behaves as expected on fresh i3 start, but after some usage it starts to behave as described until i3 restart.

Log. It started to happen after 05/12/18 15:04:??.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment