PhilippC / PhilippC/keepass2android
[BUG] Notifcations are placed on top of password field
Nobody has claimed this yet.
- 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:
There are a lot of bugs regarding notifications, but I couldn't find this one.
K2A places notifications on top of the password field, which is quite annoying. This happens especially when I type a wrong password. Instead of typing the password again or use the eye-button to see what character is wrong I have to wait till the fading message is gone. I suggest to place these messages in the big blue block on top where it doesn't interfere with any input fields or controls.
Note: I can't add a screenshot since the app (understandably) doesn't allow taking screenshots.
Describe what you expected to happen:
No response
What version of Keepass2Android are you using?
1.12-r5
Which version of Android are you on?
14
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
The issue names no files, tests, or entry points. Start by reproducing the password-entry notification on Android 14, then trace the screen's notification placement; done means the message no longer covers the password field or its controls and the behavior is regression-checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- design, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100