tiny-pilot / tiny-pilot/tinypilot
ChromeOS support treats mouse input as a touch device
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
Description
A user has reported that Chromebook interprets TinyPilot's mouse emulation as a touch device.
What's the behavior that you expect?
The ChromeOS treats the TinyPilot's input the same way it would treat an external physical mouse.
What's happening instead?
Instead of moving the cursor as the user moves the cursor on the screen, the cursor only moves when the user clicks the cursor. And scrolling can only happen when the user clicks and drags the screen like on a phone.
What are the steps to reproduce this behavior?
- Connect TinyPilot to a Chromebook
- Try moving the mouse
Screenshots
Screenshot is of a long-left click of the word "easy"
Logs
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 by reproducing the mouse behavior with TinyPilot connected to a Chromebook, using the linked logs as a reference. Trace the mouse emulation path and compare the reported ChromeOS behavior with an external physical mouse; done means cursor movement and scrolling work without click-drag gestures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- raspberry-pi
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100