PhilippC / PhilippC/keepass2android
[QUESTION] KP2A plugin confirmation dialog layout issue with external HID providers (BluKeyborg)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
I am currently developing software for a USB HID dongle for credential “typing,” similar to InputStick, but fully open-source and with stronger encryption (mTLS-encrypted payloads).
- USB dongle firmware – https://github.com/larrylart/blue_keyboard
- Android companion app – https://github.com/larrylart/blukeyborg-android
As with InputStick, I invoke the KP2A instance via an Intent to enable the plugin. However, the KP2A confirmation popup opens in full-screen/immersive mode (see attached image), and the Accept / Deny buttons end up underneath the Android system navigation bar, making them inaccessible.
Rotating the device to landscape mode makes the Accept button visible. I’ve tried all the approaches I can think of to force the dialog to fit within the visible screen area, but without success. I’m not sure whether I’m missing something on my side, or if this is simply a layout/immersive-mode quirk in KP2A?
I notice the same issue with InputStick KP2A plugin app.
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 confirmation dialog through an external HID provider Intent, using the portrait and landscape orientations described in the issue. Compare whether the Accept and Deny buttons remain accessible above the Android navigation bar; done means the confirmation controls are usable in portrait mode as well.
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