Re: [manifest] Graceful handling of no network connectivity in hosted apps (#339)

@skddc: 
> Shouldn't it at least fail gracefully, when none has been defined?

This would just be normal browser 404 behavior - so yes, it would fail gracefully... or as gracefully as the UA can make it fail. 

> Part of this could some technical ignorance, but if this is a hosted app rather than a packaged app, would there even be any JavaScript "installed" on the device to kick off the service worker?

Note: Packaged apps are outside the scope of this spec. 

The working assumption is that this specification applies to web apps, not "hosted apps" (which have thus far been outside the scope of this specification).  By "hosted app" I'm assuming you mean a web application that a manufacturer has pre-installed on a device, but never actually run. 

Controversially, Mozilla is proposing supporting "hosted app" scenarios like the one you describe through: https://github.com/w3c/manifest/issues/161
 
> Seems like such a fundamental use case that it would be nice if the manifest provided a nice abstraction so that every single app developer doesn't have to engineer the no network scenario from scratch.

This only holds true if "hosted apps" are in scope for this specification. However, it does open up a whole bunch of issues if hosted apps are in scope of this specification (e.g., declaring CSP up front too).   

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/339#issuecomment-85140990