-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
zwlr_layer_surface_v1::keyboard_interactivity v4 #7499
Comments
In particular, I want to use this for shotman, which uses this protocol. |
I think wlroots supports it: https://gitlab.freedesktop.org/wlroots/wlroots/-/commit/45c0877e3433f2b057f9125a8bc735057e088e6c |
Adding a +1 to this, given that the following PRs have made it into
Note: FWIW, there is also one for wayfire: WayfireWM/wayfire#962 Testing the quick When on these layers, it's impossible to get keyboard focus off of the demo program window without first setting keyboard setting back to "None". Not ideal from a UI/UX perspective, nor from an app developer perspective given the protocol's promise of an "On Demand" keyboard mode versus "Exclusive". |
Notes:
EDIT: I just tested building from source each package. I can confirm that the
Unless this gets backported to the |
This is a feature request for zwlr_layer_surface_v1::keyboard_interactivity v4::on_demand:
I think a suitable implementation for sway is to handle focus like a a floating window (e.g.: same mouse rules and same mapping to toggle focus).
If the previous state was
exclusive
, it initially has focus, if its previous state wasnone
, it does not.The text was updated successfully, but these errors were encountered: