PhilippC / PhilippC/keepass2android
[BUG] KP2A keyboard occasionally called up unexpectedly
Open
Nobody has claimed this yet.
bug
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
Checks
- I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:
Two different scenarios:
- URL input in the address bar of the browser
- Text input in a form.
The current keyboard changes unexpectedly to the KP2A keyboard.
Describe what you expected to happen:
The KP2A keyboard should only be called up for the corresponding input fields or by actively changing the keyboard.
What version of Keepass2Android are you using?
1.10-pre
Which version of Android are you on?
Android 14, One UI 6.0
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
Start by reproducing the behavior on Android 14 with One UI 6.0 and Keepass2Android 1.10-pre, using both a browser address bar and a form text field. Done means the KP2A keyboard appears only for corresponding input fields or after the user actively changes the keyboard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100