Multiple key presses cause unintended effects.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3k
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
If the device connects with a delay for any reason (for example, after a few seconds), the user may press Enter several times. As a result, the first press initiates the connection, and subsequent presses disconnect the device. From the point of view of UX and predictability of behavior, this seems incorrect: repeated presses made at a time when the device is actually still disconnected should not lead to the opposite effect. A more expected and consistent behavior would be to ignore repeated actions until the current connection process is complete.
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named in issue #123; start by locating the Enter-key handler and the Bluetooth connection state transition. Reproduce the delayed connection, press Enter repeatedly, and verify that additional presses are ignored until the current connection process completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust
- Domain
- cli, networking, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100