Wishlist: please hint at potential issues with the adopted browsers in the "Add a new webapp" dialog

Abierto
#396 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
desktop

Línea de trabajo

Start by reading the webapp-manager README section on browser quirks and locating the “Add a new webapp” dialog and its browser selector. Work out how the selected browser’s guidance could be shown in that dialog; done means users can see the relevant quirks while choosing a browser, including the Firefox and KDE task manager issue described here. The issue does not name files or tests.

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

Descripción

Different browsers have different takes at webapps and some more quirks are introduced by the browser+window manager combination. Some of these quirks are listed in the webapp-manager readme. Would be great to have a [?] button or a tool tip for the "browser" selector in the "Add a new webapp" dialog reporting the main quirks of the currently selected browser.

For instance, using Firefox as a browser with KDE there is a big issue in that the "KDE icons only task manager" appears to set the icon by the "program name" rather than the "window class". Hence, all the webapps get the "firefox" icon in the task manager rather than their right one. Furthermore, they get grouped with other Firefox windows, that is extremely inconvenient (now this may be an issue with the KDE plasma icon only task manager, but weirdly chrome and chromium don't have this issue).

Not having guidance in selecting the browser ends up in users picking one browser to then discover that it is too inconvenient to use, so they need to destroy the webapp and recreate it.

Lenguaje dominante
Python
Estrellas
1k
Forks
132
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 linuxmint/webapp-manager

Todos los issues de linuxmint/webapp-manager

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.