[Feature]: Add long-press popup behavior options for bottom-row functional keys
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 35/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 領域
- accessibility, frontend, mobile
調査の方向性
Read the keyboard’s key and popup handling code, then trace how bottom-row functional keys open, select from, and dismiss popups in both Alphabet and Symbols layouts and URL fields. Check existing settings and tests for long-press behavior before estimating the implementation. Done means all four options work for the listed keys, regular letter popups keep their current behavior, and Back or tapping the original key closes a popup left open.
索引モデルが issue の本文から書いたものです。
説明
Feature Screening Checklist
- I have verified this is not a personal niche workflow and benefits a wide user base.
- This cannot be achieved using existing tools (custom layouts, text expander shortcuts, user dictionaries, or system settings).
- This will not introduce typing lag, delay loops, or degrade typing responsiveness on low-end devices.
- I have searched existing open and closed issues and discussions to confirm this has not been requested or rejected before.
Problem Statement
Currently, when a user long-presses a key that has a popup (such as the period, comma, slash key in URL fields, or the language/globe key), the popup behavior is limited to one mode: the user must slide to an option and release their finger to insert it. Once the item is selected, the popup closes immediately.
Some users prefer a two-step selection flow: long-press the key, lift the finger to keep the popup open, then tap the desired item. In Samsung Keyboard, this popup can remain open even after selecting an item, which is useful when the user wants to insert multiple items from the same popup. However, other users may want the popup to remain open only until they make one selection, then close automatically.
A hybrid behavior would also be useful: the popup remains open after lifting the finger, but it closes immediately after the user selects an item, whether the selection is made by sliding while the finger is still down or by tapping after lifting the finger.
At present, LeanType does not offer a setting to choose between these long-press popup behaviors for bottom-row functional keys.
Proposed Solution
Add a setting called “Long-press popup behavior” that controls the popup behavior for all bottom-row functional keys that have a long-press popup.
This includes the Enter/Action key, period key, space key, comma key, and language/globe key. It should also apply to the slash and period keys when they appear in URL input fields.
This setting should apply in both the Alphabet layout and the Symbols layout, and to the language/globe key wherever it is available.
This setting should not change the behavior of regular letter keys or their alternate-character popups. Letter keys should continue using the normal long-press behavior: slide to an alternate character and release to insert it, then close the popup.
Provide four options:
-
Close after selection (current default)
Long-press a key to open its popup. Slide to an item and release. The selected item is inserted or its action is performed, and the popup closes immediately. -
Keep open after selection (Samsung Keyboard-like)
Long-press a key, then lift the finger without selecting anything. The popup remains open. Tap an item to insert it or perform its action. After that, the popup remains open. -
Keep open before selection, close after selection
Long-press a key, then lift the finger without selecting anything. The popup remains open. Tap an item to insert it or perform its action. After that, the popup closes immediately. -
Hybrid: close after selection
Long-press a key to open its popup.
If the user slides to an item while keeping their finger on the screen and then releases, the selected item is inserted or its action is performed, and the popup closes immediately. This is the current default behavior.
If the user lifts their finger before selecting an item, the popup remains open. Then, when the user taps an item, the selected item is inserted or its action is performed, and the popup closes immediately.
For Options 2, 3, and 4, when the popup remains open after lifting the finger, tapping the same original key again should close the popup. Android Back and the back gesture should also close it.
Suggested setting label:
Long-press popup behavior
- Close after selection (default)
- Keep open after selection
- Keep open before selection, close after selection
- Hybrid: close after selection
Reference videos from Samsung Keyboard:
1
https://recordit.dev/record/b7b65a94-b8e8-46d0-bd68-6be1f3513753
2
https://recordit.dev/record/db2311ee-9a82-4cf8-9d30-ec60de5211e1
Target Audience & Benefits
Target audience:
Users who frequently type in Arabic and other languages that use diacritics, punctuation, symbols, multiple languages, or URL fields. It is especially useful for users who often insert several diacritics, symbols, domains, or language-related actions from the same long-press popup.
Benefits:
- Gives users control over long-press popup behavior instead of forcing one interaction model on everyone.
- Improves typing precision by letting users open the popup, lift their finger, and carefully tap the desired item.
- Reduces repeated long-presses when a user needs to insert multiple items from the same popup, particularly in Option 2.
- Preserves the current fast, familiar behavior as the default, so existing users are not affected unless they choose another option.
- Keeps the feature lightweight: it changes only the popup dismissal/selection flow for a small, clearly defined set of bottom-row functional keys, without adding background processes, typing latency, or complex maintenance.
- Offers a hybrid interaction model: users can lift their finger to keep the popup open for more precise tapping, while the popup still closes immediately after a selection, avoiding an unnecessarily persistent popup.
Alternatives & Workarounds Considered
No response
- 主要言語
- Kotlin
- スター
- 1k
- フォーク
- 59
- 平均マージ
- 5時間 44分
- マージ済み PR(30日)
- 59
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
LeanBitLab/LeanType のほかの issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
LeanBitLab/LeanType#864 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 3/5 1〜2日 初心者へのやさしさ 56/100
LeanBitLab/LeanType#861 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
enhancement
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
LeanBitLab/LeanType#853 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
[Bug]: CJK Japanese input resets to Chinese after switching apps (physical keyboard)対応中かも @LeanBitLab が 2 日前に担当しました。 オープンbug
LeanBitLab/LeanType#842 · コメント 18 件 · 担当者 1 名 ·
メンテナーはふだん 1 日以内に返信
-
Notesオープンdocumentation
難易度 3/5 1〜3時間 初心者へのやさしさ 15/100
LeanBitLab/LeanType#804 ·
メンテナーはふだん 1 日以内に返信
LeanBitLab/LeanType の issue をすべて見る
似ている issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 61/100
PixelPlayerHQ/PixelPlayerOSS#249 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
streetcomplete/StreetComplete#7395 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 82/100
134130/intellij-mise#552 ·
-
enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
wasi-master/wmkeyboard#1443 ·