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

As it sounds like a lot of the disagreement is around having the manifest now being in charge of caching something. What if instead of assuming that `offline_page` will do some sort of caching, it's rather closer to how `start_url` works where it doesn't own caching but rather tells what _should_ be used. This I think would still solve most of the problems I see that had me propose this (increasing visibility of this UX aspect, providing a tooling hook) and reduce the overhead to developers by only requiring them to ensure that that particular URL is cached. Caching is still controlled by SW, but manifest lets browsers know what it _should_ use.

-- 
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-515566648