wayland: does not properly track keyboard and pointer focus
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9.7k
- Forks
- 565
- PR merge metrics
- No merged PRs in 30d
Description
At the moment the wayland backend just tracks if a surface has focus. Using the `multiwin` example in druid, spawning another window and moving the cursor to the new window will result in the wrong window showing hover events.
Eli5: the wayland backend needs to store what surface is focused and send input events to that surface.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Wayland backend and reproduce the issue using the `multiwin` example by opening another window and moving the cursor between them. Trace how keyboard and pointer focus are tracked and how input events are routed. Done means events go to the surface that currently has focus, so hover events appear on the correct window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100