[virtwl] Input not working under vscode with certain settings
- Dominant language
- Rust
- Stars
- 27
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
A user has reported to me personally that input in vscode is not working. vs code ignores all the keys (i.e. keypress has no effect on vscode's behavior).
User note the following settings might be related:
1. focus-follows-mouse enabled (chrome://flags/#focus-follows-cursor)
2. In vscode, `"keyboard.dispatch": "keyCode",.`
A vscode CUJ has been tested (with IME enabled, turned both on and off) on a chromebook before the current release (v0.2.0-virtwl) was cut. Need to check if these settings affect keyboard. It also sounds like with these settings, original sommelier worked (not sure if the user did `--ozone-platform=wayland` when using vscode with original sommelier)
Contributor guide
Research direction
Reproduce the report with Sommelier v0.2.0-virtwl and VS Code, testing focus-follows-mouse, "keyboard.dispatch": "keyCode", and IME enabled or disabled. Compare the behavior with original Sommelier and determine whether --ozone-platform=wayland changes the result; done means keyboard input works under the reported settings or the affected path is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100