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

KDE Workaround to focus issues #2026

Open
gfgit opened this issue Feb 17, 2024 · 6 comments
Open

KDE Workaround to focus issues #2026

gfgit opened this issue Feb 17, 2024 · 6 comments

Comments

@gfgit
Copy link
Member

gfgit commented Feb 17, 2024

In #1975 we hit QTBUG-52021

This is because panel window does not accept focus (See panel/lxqtpanel.cpp#L152)

This line was added inside commit 63accd3

Current situation:

@tsujan
Copy link
Member

tsujan commented Feb 17, 2024

Is this our issue? If yes, please describe it. If no, https://github.com/lxqt/lxqt/discussions is the best place for it.

EDIT:
Thanks for adding an explanation to your report!

@stefonarch
Copy link
Member

stefonarch commented Feb 18, 2024

If I get things right also on wayland a panel should not have focus while atm lxqt-panel takes focus if clicked somewhere, menu or not, while waybar, yatbfw or sfwbar do not, so this commit doesn't ever work on wayland, x11 only. But they have no menu to write or search in.

On wayland with layershell-qt this is can be achieved using

    /**
     * This enum type is used to specify how the layer surface handles keyboard focus.
     */
    enum KeyboardInteractivity {
        KeyboardInteractivityNone = 0,
        KeyboardInteractivityExclusive = 1,
        KeyboardInteractivityOnDemand = 2,
    };

@tsujan
Copy link
Member

tsujan commented Oct 24, 2024

Window::KeyboardInteractivityNone had a nasty problem that prevented the panel's children from getting the focus.

Now, at least with Qt 6.8 and under kwin_wayland, it works like a charm, such that I was able to remove the workaround mentioned in #2116 here.

@stefonarch
You have a complete collection of Wayland compositors. Would you test it under them and see if the children can get the focus? If it works with well-known compositors that are important to us, we could use it and get rid of a focused panel under Wayland.

@stefonarch
Copy link
Member

stefonarch commented Oct 24, 2024

I tested all (except kwin which you did afaik).
Unfortunately only wayfire and Hyprland give focus to the menus (arrow keys and input field in Fancy menu), river, sway, niri and labwc not.

Don't know if we can change to OnDemand on opening menus.

@tsujan
Copy link
Member

tsujan commented Oct 24, 2024

Unfortunately only wayfire and Hyprland give focus to the menus

And kwin_wayland.

I'm getting suspicious of a problem in the other compositors, including my favorite, labwc.

@tsujan
Copy link
Member

tsujan commented Oct 25, 2024

Done in 0d0d14b, for well-behaving Wayland compositors like kwin_wayland.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants