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

Focus does not follow mouse #3639

Open
Ceda-EI opened this Issue Mar 8, 2019 · 3 comments

Comments

Projects
None yet
3 participants
@Ceda-EI
Copy link

Ceda-EI commented Mar 8, 2019

I'm submitting a…

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

Current Behavior

When I move mouse from primary display to secondary display, the app under cursor doesn't get focus. (focus_follows_mouse yes is set)
for_window [class="^.*"] border pixel 1 is the culprit.

Expected Behavior

When I move mouse from primary display to secondary display, the app under cursor should get focus.

Reproduction Instructions

  • Add for_window [class="^.*"] border pixel 1 and focus_follows_mouse yes to config.
  • Open 1 window on the secondary monitor.
  • Move mouse from primary monitor to secondary monitor.

Environment

Output of i3 --moreversion 2>&-:

Binary i3 version:  4.16.1 (2019-01-27) © 2009 Michael Stapelberg and contributors
(Getting version from running i3, press ctrl-c to abort…)
Running i3 version: 4.16.1 (2019-01-27) (pid 24627)
Loaded i3 config: /home/ceda/.config/i3/config (Last modified: Fri 08 Mar 2019 02:56:35 PM IST, 700 seconds ago)

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

@i3bot i3bot added the bug label Mar 8, 2019

@i3bot

This comment has been minimized.

Copy link

i3bot commented Mar 8, 2019

I don’t see a link to logs.i3wm.org. Did you follow https://i3wm.org/docs/debugging.html? (In case you actually provided a link to a logfile, please ignore me.)

@Airblader

This comment has been minimized.

Copy link
Member

Airblader commented Mar 8, 2019

I'm having trouble with this issue since border 1 is not a valid command. Can you try what happens when you actually use a valid command like border pixel 1?

@Ceda-EI

This comment has been minimized.

Copy link
Author

Ceda-EI commented Mar 8, 2019

The actual line was border pixel 1. That was a typo. Updated the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.