Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

UI exploration: consistent UI pattern for user confirmation

Abierto
#1,683 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
html
Área
design, documentation, frontend

Línea de trabajo

Review app/templates/custom-elements/security-dialog.html and the linked Static IP change, then inventory confirmation behavior for the other listed dialogs and destructive actions. Define the desired confirmation pattern in the style guide and apply the agreed rules throughout the UI; completion should cover the listed operations consistently.

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

Descripción

enhancement medium

I don’t think we follow a deliberate pattern in the UI as to when we require confirmation after button clicks in dialogs. E.g.:

  • In the upcoming “Static IP” feature, we’ll have a separate confirmation prompt before removing the static IP address.
  • In the <security-dialog> component, we have a confirmation prompt when toggling off the auth requirement.
  • Apart from that, I don’t think we have such a confirmation in any of our other dialogs, including the ones that carry out destructive and potentially “harmful” operations, such as:
    • Removing individual users
    • Disabling the HTTPS enforcement
    • Changing the hostname (which causes a device reboot)
    • Removing disk images (which are potentially very slow to upload)

Not having any confirmation for these kinds of operations actually makes me feel slightly uneasy. (I’m not sure how e.g. customers feel about that, though, or whether we have ever received “angry” feedback about this.)

In any event, I think we should define our desired UX pattern for user confirmation in the style guide, and then roll out the rules in the entire UI.

UI-wise, there are different patterns for user confirmation. Apart from the aforementioned separate confirmation step/prompt, there are also more light-weight patterns we could consider.

Lenguaje dominante
Python
Estrellas
3.5k
Forks
291
Sin PR fusionados en 30 d

Guía de contribución

Abrir la guía de contribución

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 tiny-pilot/tinypilot

Todos los issues de tiny-pilot/tinypilot

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.