[Feature request]: Feedback and UX Friction Points on Flatpak PWA Integration, File System Permissions, and Icon/WMClass Resolution
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 15/100
Rechercherichtung
This is a broad feedback report, not a defined change, and the body names no source file, test or entry point. Before any code, a newcomer would need a maintainer to decide which of the three points (sandbox file access for PWA shortcuts, Icon= paths, StartupWMClass= matching) is in scope for Flatpak itself. Done would mean a narrowed, agreed proposal, not a patch.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Checklist
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Suggestion
Dear Flatpak Development Team,
I am writing to share feedback and practical solutions regarding the user experience and integration of Progressive Web Apps (PWAs) installed via browser Flatpaks (Google Chrome, Brave, and Microsoft Edge) on Linux desktop environments (specifically GNOME/Ubuntu).
While Flatpak provides an exceptional and secure sandboxing model, we encountered specific friction points during PWA deployments that require manual workarounds. I would like to outline these challenges and the solutions we successfully implemented:
- File System Access for PWA Creation
The Issue: When attempting to create or install a PWA from within a sandboxed browser (e.g., Chrome or Edge), the browser throws an error stating it lacks write access to ~/.local/share/applications and ~/.local/share/icons, preventing automatic .desktop file and icon creation.
The Solution / Request: Native PWA installation flows should ideally have a standardized, seamless permission bridge or portal interaction to provision shortcuts in standard user directories without forcing users to rely on external tools like Flatseal or manual filesystem overrides (--filesystem=xdg-data/applications).
- PWA Icon Resolution Pathing
The Issue: Browser Flatpaks store internal PWA assets (such as high-res icons like 512.png or 256.png) deep within the sandbox under ~/.var/app//config/.../Manifest Resources//Icons/. By default, generated .desktop entries sometimes look for system-wide icon paths, causing missing icons.
The Solution: Pointing the Icon= field in .desktop files directly to the internal browser manifest resource path ensures persistent, highest-resolution icon rendering (prioritizing 512px/256px) that survives browser and PWA updates automatically.
- Window Management and Dock Grouping (StartupWMClass)
The Issue: Launched PWAs often fail to detach from their parent browser on the desktop dock (Dash to Dock), grouping under the main browser icon instead of displaying their dedicated PWA icon due to a mismatch in window class identification.
The Solution: Explicitly matching or aligning the StartupWMClass= field inside the .desktop entries to match the browser's specific PWA window signature (e.g., chrome--Default or crx__) successfully forces the desktop environment to treat PWAs as independent, standalone applications.
I hope this feedback helps improve the out-of-the-box PWA support and integration for Flatpak-packaged browsers in future releases. Thank you for your incredible work on Flatpak.
Best regards,
Ilya
- Vorherrschende Sprache
- C
- Sterne
- 5.1k
- Forks
- 526
- Ø Merge
- 3 T. 1 Std.
- Gemergte PRs (30 T.)
- 23
Entwicklungsumgebung
Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus flatpak/flatpak
-
[Feature request]: remove flatpak.fish completion so the shell's own completions are usedEvtl. vergeben @Franklin-Qi hat das vor 33 Tagen übernommen. Offenenhancement needs triage
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 75/100
Maintainer antworten meist innerhalb von 1 Tag
-
needs triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Maintainer antworten meist innerhalb von 1 Tag
-
[Feature request]: add support for `xdg-state` filesystem prefixEvtl. vergeben @Franklin-Qi hat das vor 33 Tagen übernommen. Offenenhancement libflatpak
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
flatpak/flatpak#5958 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
cli enhancement low priority
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
Maintainer antworten meist innerhalb von 1 Tag
-
Some flatpak repair strings are not translatableEvtl. wieder frei Ein Pull Request dazu wurde ohne Merge geschlossen. Offen
Schwierigkeit 2/5 Unter einer Stunde Anfängerfreundlichkeit 65/100
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in flatpak/flatpak
Ähnliche Issues
-
[issue]: Ventoy2Disk.sh can leave the end of VTOYEFI unwritten (xzcat | dd without iflag=fullblock)Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 73/100
prusa3d/Prusa-Firmware-Buddy#5629 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
stratum-mining/sv2-tp#167 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 85/100
libsdl-org/SDL_ttf#650 ·
-
HTTP Request Smuggling: non-final chunked Transfer-Encoding not rejected (CWE-444)Evtl. vergeben @code1a2024 hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 77/100