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

[BUG] The extension breaks Gnome Shell sloppy focus and raise window delay #44

Closed
tukanos opened this issue Sep 23, 2022 · 4 comments
Closed
Labels
needs more information Further information is requested

Comments

@tukanos
Copy link

tukanos commented Sep 23, 2022

Describe the bug
After lengthy debugging and help of FeRD (Frank Dana) @ferdnyc - the original ticket is here. I have found out that AATWS - Advanced Alt-Tab Window Switcher breaks the Gnome Shell's sloppy focus (now called differently) and raise window delay functionality.

The functionality does not work at all. I'm reporting it as one issue as it seems these two issues are closely connected. If you want to create 2 issues I can.

The GNOME Shell version is 42.4

To Reproduce
I) Steps to reproduce the behavior:

  1. Switch on the AATWS
  2. Go to the Gnome Tweaks window and the Windows tab
  3. There select Focus on Hover OR Secondary-Click
  4. Raise Windows When Focused is turned on
  5. Both these functionalities do not work correctly afterwards. The work the same way for both but the difference should be:
    5a) Focus on Hover - Window is focused when hovered with pointer. Windows remain focused when the desktop is hovered
    5b) Secondary-Click - Window is focused when hovered with pointer. Hovering the desktop removes focus from the previous window.

II) The delay in the window focus

  1. Switch on the AATWS
  2. in dconf-editor, navigate to /org/gnome/desktop/wm/preferences/auto-raise-delay
  3. change the default value to, for example, 2000ms
  4. Test the window raise delay. The windows are still raised immediately ignoring the delay value

Expected behavior
Focus on Hover - Window is focused when hovered with pointer. Windows remain focused when the desktop is hovered
Secondary-Click - Window is focused when hovered with pointer. Hovering the desktop removes focus from the previous window.

For the window raise delay to be obeyed.

Desktop (please complete the following information):
-- System Information:

Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

  • Version of the extension: 20
  • Source of installation I think it was GitHub but not 100% sure.
@G-dH
Copy link
Owner

G-dH commented Sep 23, 2022

Thanks for the report. The only AATWS option that affects window manager behavior is Always Activate Focused Window on the Misc tab of the Settings window and if it's enabled you had to do it yourself. When it comes to the Secondary-Click focus issue, it never removes focus from a window when the pointer hovers over a Desktop, on any of my systems (Ubuntu, Fedora, no DING), no matter whether the AATWS is enabled.

@G-dH G-dH added the needs more information Further information is requested label Sep 25, 2022
G-dH added a commit that referenced this issue Sep 25, 2022
@tukanos
Copy link
Author

tukanos commented Sep 26, 2022

I see, I'm sure I have enabled it myself. At the beginning when using the plugin I was playing around with the settings and forgot about it.

Thank you for clearing up the issue. After unchecking the "hack" option it started working as it should.

@tukanos tukanos closed this as completed Sep 26, 2022
@G-dH
Copy link
Owner

G-dH commented Sep 26, 2022

I've fixed the issue so now the option shouldn't rise windows.

@tukanos
Copy link
Author

tukanos commented Sep 27, 2022

I've fixed the issue so now the option shouldn't rise windows.

Thank you for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more information Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants