On 12 June 2015 at 18:41, Benjamin Francis <[email protected]> wrote:
> Yeah that's really what I'm getting at. Do we still need > window.navigator.mozApps.install() ? If not then how do we do all the other > things that we currently register at install time? Do we need new > (internal?) APIs for those things? > > * activities > * appcache_path (I guess we will deprecate this, but we might want to > replace it with service worker integration) > * customizations (I guess we can keep this for the manifests of addons) > * datastores-owned/datastores-access (I hope we can deprecate DataStore > eventually but we need it for now) > * fullscreen (I think we can replace this with display_mode and handle it > in Gaia for pinned sites only) > * messages (as you mentioned) > * orientation (I think we can support this in Gaia for pinned sites) > I'm starting to talk to myself a little bit now (sorry), but it occurs to me that maybe it's only pinning Firefox Apps (i.e. Firefox specific signed content) that Gecko needs to know about, I can't think of any reason Gecko needs to know when the user pins a web app/web site. Maybe we need to keep the Apps API for Firefox Apps (and addons), and web apps can be handled entirely in Gaia? Is there some reason Gecko needs to know when a web app/web site is pinned? Web apps can't use proprietary APIs like Web Activities, Data Stores and system messages that need registering at pin time. Are there any differences in storage quotas etc. that mean Gecko needs to know? Maybe if we added Service Worker integration into the manifest Gaia would need a way to trigger a Service Worker registration in Gecko? With the current approach to app scope we can get away with not needing to register scope with Gecko. Ben
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
