Long-pressing keys in the Android shortcut bar dismisses the keyboard and provides no haptic feedback
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- android, javascript
- Domain
- mobile
Research direction
Start by reproducing the issue on Android 16 with Fcitx5 Android, then locate the shortcut bar's long-press handling and related keyboard visibility or haptic-feedback behavior. Done means long-pressing a shortcut key keeps the keyboard visible, performs the intended action when supported, and provides haptic feedback when enabled.
Written by the indexing model from the issue text.
Description
Description
When using electerm on Android to connect to an SSH server, the keyboard shortcut bar does not appear to support long-press interactions correctly.
Long-pressing a key in the shortcut bar causes the Android on-screen keyboard to disappear. In addition, there is no vibration or other haptic feedback to indicate that the long-press has been recognized.
Steps to Reproduce
- Open electerm on an Android device.
- Connect to an SSH server.
- Open the Android on-screen keyboard.
- Long-press any key in electerm’s keyboard shortcut bar.
Actual Behavior
- The Android keyboard closes or disappears.
- No vibration or haptic feedback is provided.
- The long-press action does not appear to work as expected.
Expected Behavior
- Long-pressing a shortcut-bar key should trigger the intended long-press action, if supported.
- The Android keyboard should remain visible unless the user explicitly dismisses it.
- Haptic feedback should be provided, if enabled by the device and system settings.
Environment
- App: electerm for Android
- Connection type: SSH
- Android version: 16
- electerm version: 5.5.35
- Keyboard app: Fcitx5 Android
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 1
- Avg merge
- 12h 18m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from electerm/electerm-android
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
electerm/electerm-android#8 · 1 comment ·
-
obtainium supportOpen
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
electerm/electerm-android#4 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
electerm/electerm-android#3 · 1 comment ·
All issues in electerm/electerm-android
Similar issues
-
[Feature]:Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
automated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
lirantal/discoprint#36 ·
Maintainers usually reply within 1 day
-
accepting PR Content:HTML
Difficulty 1/5 Under an hour Newbie friendliness 88/100
mdn/content#45988 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
txn2/mcp-data-platform#2030 ·
Maintainers usually reply within 1 day