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

layer surface 'on_demand' keyboard focus does not receive focus until the user clicks on it. #1276

Closed
marcusbritanicus opened this issue Sep 6, 2021 · 4 comments · Fixed by #1986
Labels

Comments

@marcusbritanicus
Copy link
Contributor

Describe the bug
If we have a client that uses layer shell protocol, and set the keyboard focus to on_demand, it does not get the keyboard focus until the user clicks on it.

To Reproduce
Steps to reproduce the behavior:

  1. Open a client that uses layer shell protocol and requires on_demand keyboard focus.
  2. You'll see that it does not have keyboard focus, until you click it with a mouse pointer.

Expected behavior
Give keyboard focus to the layer surface as soon as it is mapped.

Wayfire version
git

PS: This was tested using a Qt app. It is possible that this bug is due to Qt's bad implementation of things.

@marcusbritanicus
Copy link
Contributor Author

I can confirm that this is a wayfire bug and not due to Qt. I tested my drop-down terminal with on_demand keyboard focus on sway. It receives keyboard focus as soon as it is shown.

@mfxbe
Copy link
Contributor

mfxbe commented Oct 29, 2023

Just run into this issue with gtk4-layer-shell as well. exclusive-mode does work but with on_demand the the surfaces never gets the focus unless its done manually by the user.

@ammen99
Copy link
Member

ammen99 commented Oct 29, 2023

We probably need the same as #1933 in the map handler of layer-shell views.

@mfxbe
Copy link
Contributor

mfxbe commented Oct 29, 2023

That does indeed (#1986) fix it.

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

Successfully merging a pull request may close this issue.

3 participants