| Summary: | Requesting NO Touch Capability captures touch events | ||
|---|---|---|---|
| Product: | [Plasma] xdg-desktop-portal-kde | Reporter: | ferdinandschober20 <ferdinandschober20> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | aleixpol, kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
ferdinandschober20@gmail.com
2024-10-18 14:36:56 UTC
Sorry, I confused OBSERVERD and EXPECTED result here. Should be swapped. I am not sure this is how it is supposed to work. I think the capabilities is about what the impl can provide to you and what you can consume and then expect. I think it also results in a better UX. What happens if you capture Pointer but not keyboard? I can still use it on the main PC but not move the focus anywhere with the mouse because it is captured. How would a capture look like that does the reverse, capture keyboard when the pointer crosses the barrier but not the pointer. I think you can get into situations that are confusing to the user very quick. So I think blocking everything on the host when a capture starts makes sense. |