Re: [w3c/manifest] Add offline_url option (#774)

Sure, and yes I do understand that it's duplicative of what you can do with Service Workers.

Recently, I've found a number high-profile PWAs that present browser-default offline pages, which breaks the app-like experience that PWAs promise. The thinking here is that Service Workers are still hard to work with and configuring them in all the myriad ways one can _and_ ensuring that a custom offline page is always served appears to still be a challenge for developers. Having a stand-alone property for this that's as simple as passing a URL I believe would greatly increase the chance that PWAs provide the desired native-like offline experience, both by reducing the development cost of doing so and by making it highly visible.

In addition, I believe this could improve tooling for PWAs; currently, there isn't a good way to generally ensure that a PWA never shows the default offline page. Having this property would give tooling a way to suggest a way of supporting that.

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