Support password manager autofill on the login page

Abierto
#4,780 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, cpp, ios
Área
mobile

Línea de trabajo

Start by reading the login and SSO form implementations and related issue #1654; the payload does not name their file paths. Check how the email and password fields are configured for device password managers on iOS and Android. Done means credentials are offered from either login field and fill both fields, while the SSO email field offers saved emails.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

android 🤖 auth enhancement iOS 🍎

Current situation

Saved credentials are not fully offered on the login page:

  • iOS: the Passwords suggestion above the keyboard only appears for the password field, not the email field and when tapping on the credential, it only autofills the password, not the email field.
  • Android (Gboard + Google Password Manager): no suggestion appears for either field

Users have to type their email (and on Android, their password) manually.

Solution

Make the login form work with the device's password manager, so saved credentials are offered from both the email and password fields.

Acceptance criteria

  • Tapping the email or password field on the login page offers saved credentials from device's password manager
  • Selecting a suggestion fills both the email and password fields
  • The email field on the SSO page offers saved emails as well
Related issues
  • #1654
Lenguaje dominante
C++
Estrellas
394
Forks
91
Merge medio
2 d 10 h
PR fusionados (30 d)
16

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de MerginMaps/mobile

Todos los issues de MerginMaps/mobile

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.