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

Offen
#340 3 Kommentare 2 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
desktop

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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!

Vorherrschende Sprache
Python
Sterne
1k
Forks
132
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus linuxmint/webapp-manager

Alle Issues in linuxmint/webapp-manager

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.