Kunzisoft / Kunzisoft/KeePassDX
Consider using `getAutofillHints()` to determine whether we need to do autofill
- Dominant language
- Kotlin
- Stars
- 7.3k
- Forks
- 401
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
The Autofill was triggered in the wrong input view, such as Termux's terminal, which set AutofillHints to AUTOFILL_TYPE_NONE.[^1]
**Describe the solution you'd like**
Use `getAutofillHints()` to determine whether we need to do autofill here.
**Additional context**
For all AutofillHints values, see https://developer.android.com/reference/android/view/View#setAutofillHints(java.lang.String[])
For `getAutofillHints()`, I found two, but don't know which one is used by the autofill service, see https://developer.android.com/reference/android/app/assist/AssistStructure.ViewNode#getAutofillHints() and https://developer.android.com/reference/android/view/View#getAutofillHints()
[^1]: https://github.com/termux/termux-app/blob/fb01127ff2c95f6fa5f86a77956ca2d68afad9a9/terminal-view/src/main/java/com/termux/view/TerminalView.java#L101
Contributor guide
Research direction
Start by comparing Android's View.getAutofillHints() with AssistStructure.ViewNode.getAutofillHints(), using the Android API references linked in the issue. Review the Termux TerminalView.java example to understand the AUTOFILL_TYPE_NONE case. Done means autofill is not triggered for views without applicable hints and existing autofill behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- authentication, mobile
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100