-
Notifications
You must be signed in to change notification settings - Fork 168
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
XWayland keyboard grab protocol #1093
Conversation
558c092
to
d443a67
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
aa79729
to
c970dbf
Compare
Would it be better for Smithay to call Or it could provide a default implementation for the |
Default implementation is fine, but given the protocol explicitly does not guarantee the grab to be set and suggest compositors might even show indicators for keys being captured, I say this should be compositor policy. |
c970dbf
to
e1a04b5
Compare
This protocol is only exposed to the X server, as required by the protocol spec.
e1a04b5
to
fe9beab
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #1093 +/- ##
==========================================
- Coverage 24.01% 24.01% -0.01%
==========================================
Files 140 140
Lines 21589 21591 +2
==========================================
- Hits 5185 5184 -1
- Misses 16404 16407 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.