Lower Fields in Contact creation are obstructed by Keyboard
Los mantenedores suelen responder en 4 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 45/100
Línea de trabajo
The bug is in the contact creation screen of this Kotlin Android app, so start there and find how it handles the soft keyboard and window insets. Reproduce on an emulator or small-screen device by opening Add Contact and focusing a lower field such as email. Done when the screen scrolls so the focused field stays visible above the keyboard, with no regression on the other contact screens.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Checklist
- I can reproduce the bug with the latest version given here.
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.6.0
Affected Android/Custom ROM version
Android 15/PixelOS
Affected device model
Xiaomi Mi 10T Lite
How did you install the app?
Google Play Store
Steps to reproduce the bug
Open the app
Add a new Contact
Add information in a field on the lower part of the screen
Expected behavior
The Screen scrolls up such that i can see what is typed in the field.
The field is not covered by the Keyboard.
Actual behavior
currently the field in which i want to type the email is under the keyboard, i can still type in it, but cannot see anything.
the interface has to move upwards to always show the field in which the cursor is positioned
Screenshots/Screen recordings
Additional information
No response
- Lenguaje dominante
- Kotlin
- Estrellas
- 917
- Forks
- 73
- Merge medio
- 5 d 8 h
- PR fusionados (30 d)
- 7
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FossifyOrg/Contacts
-
feature request needs triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
FossifyOrg/Contacts#176 · 1 comentario ·
Los mantenedores suelen responder en 4 días
-
bug needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 64/100
FossifyOrg/Contacts#618 ·
Los mantenedores suelen responder en 4 días
-
feature request needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
FossifyOrg/Contacts#614 · 1 comentario ·
Los mantenedores suelen responder en 4 días
-
New field: IBANAbiertofeature request needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
FossifyOrg/Contacts#613 ·
Los mantenedores suelen responder en 4 días
-
bug needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
FossifyOrg/Contacts#612 · 5 comentarios · 1 reacción ·
Los mantenedores suelen responder en 4 días
Todos los issues de FossifyOrg/Contacts
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
callstack/react-native-brownfield#492 · 1 comentario ·
Los mantenedores suelen responder en 4 días
-
fix: retain the best partial noise-correction solutionPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
world-federation-of-advertisers/cross-media-measurement#4653 ·
Los mantenedores suelen responder en 1 día
-
enhancement help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
kabirvashisht4-glitch/Vet#22 ·
-
documentation good first issue
Dificultad 1/5 1-3 horas Aptitud para principiantes 85/100
djazairdev/wilayas#23 ·
Los mantenedores suelen responder en 1 día