Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)

JerryJWChan left a comment (w3c/manifest#1191)

The core reason this proposal deserves consideration is that mobile users
expect Progressive Web Apps (installed on their home screens) to behave
similarly to native applications. However, when users clear their browser
data—often intentionally to free space or protect privacy—they are usually
unaware that this action also removes essential data and cached resources
shared by their installed PWAs.

As a result, PWAs may suddenly stop functioning as expected, leaving users
confused about the cause. This disconnect between user expectations and
actual behavior creates a negative user experience and undermines
confidence in PWAs as a reliable alternative to native apps.

The proposed solution offers an effective way to address this issue by
ensuring that PWAs can gracefully handle data loss scenarios, while also
providing users with clear information and guidance on how to recover. This
approach minimizes disruption and helps maintain a consistent and
trustworthy PWA experience.

On Wed, Oct 29, 2025 at 5:45 PM Christian Liebel ***@***.***>
wrote:

> *christianliebel* left a comment (w3c/manifest#1191)
> <https://github.com/w3c/manifest/issues/1191#issuecomment-3460623515>
>
> I’m not sure if we actually need to address this, since the situation is
> only “unrecoverable” while the user is offline. If it’s the user’s intent
> to clear site data, this should include everything, including potential
> fallback handlers. Offline fallback screens are implemented on both the
> Chromium and the WebKit side at least on desktops (see below), so I don’t
> quite see the benefit of providing a custom UI.
> Screenshot.2025-10-29.at.09.49.28.png (view on web)
> <https://github.com/user-attachments/assets/9d0751fa-eb89-4e0d-a843-41b45067c85c> Screenshot.2025-10-29.at.09.50.12.png
> (view on web)
> <https://github.com/user-attachments/assets/855e839f-c027-4541-8b46-6ff55f7818ce>
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/manifest/issues/1191#issuecomment-3460623515>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AI3TCOG6LL4XOVJU5D5VTTD32CEC5AVCNFSM6AAAAACKHEWGQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINRQGYZDGNJRGU>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1191#issuecomment-3466094105
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1191/3466094105@github.com>