Feature request: Add Option to Use Website favicon Instead of User-Provided Icon

Abierto
#340 3 comentarios 2 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
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
desktop

Línea de trabajo

Start by reading the web app creation and icon selection flows to find where URLs and user-provided icons are handled. The issue proposes favicon detection, a selectable icon source, and a fallback, but names no files or tests; completion would require defining and implementing those behaviors, including a way to refresh the favicon.

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

Descripción

First, I’d like to extend my gratitude for all the hard work you’ve put into this project—it’s been incredibly helpful and I truly appreciate the time and effort you’ve invested. I was using a PWA add-on for Firefox, but this way better.

I’d like to propose a new feature that I believe could enhance the user experience: the ability for the web app to automatically detect and use the favicon from a website as an icon option, rather than requiring users to provide their own icons.

Problem Statement:

Currently, users must manually upload or select an icon for each app. The "Find Icon Online" functionality is great, but I have noticed that it does not reliably find the icons for each site I tried so far.

Suggested Implementation:

  • Automatic Favicon Detection: When a user enters URL, the favicon associated with that website could automatically detect and fetch.
  • Selectable Option: Provide an option in the settings or configuration to choose between using a user-uploaded icon or the website’s favicon.
  • Fallback Mechanism: If the favicon is not available, not detectable, or not suitable (e.g., too small or low quality), the app could default to a generic icon or allow the user to upload their own. The favicon does not need to be queried every time, manually triggering an update would be sufficient.

Benefits:

  • Improved User Experience: Users would no longer need to hunt for and upload icons, saving them time and effort.
  • Streamlined Setup: This feature would make setting up new web applications faster and more straightforward.
  • Consistency: Using the website’s favicon is the same experience a use would have when using the browser.

I believe this feature would be a great addition to the project and would appreciate your thoughts on it. I understand that your time is valuable, so I wanted to present this idea for your consideration.

Thank you once again for your hard work and for building such a fantastic tool!

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.