[Feature request]: Feedback and UX Friction Points on Flatpak PWA Integration, File System Permissions, and Icon/WMClass Resolution

Offen
#6,972 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

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
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
linux, ubuntu
Bereich
desktop, security

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

enhancement needs triage
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:

  1. 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).

  1. 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.

  1. 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

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

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 flatpak/flatpak

Alle Issues in flatpak/flatpak

Ähnliche Issues

Weitere Issues zu C

Neue Issues direkt in Ihr Postfach

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