On Fri, Jun 12, 2015 at 10:41 AM, Benjamin Francis <[email protected]> wrote: > On 12 June 2015 at 04:46, Paul Theriault <[email protected]> wrote: >> >> Thats correct. Though you are mixing things up a little here by throwing >> in Activities. That’s not a permission, that’s just something that is >> registered at install time. (In the same way that system message listeners >> are declared). Without an install step, we will need a new way for apps to >> register anything that was previously registered in the manifest that we >> want to continue to support. > > > 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?
We will definitely need a FirefoxOS-specific API which tracks the list of URLs that have been bookmarked, and which maybe caches manifest information as needed. Likely this API would also need to send notifications when pins are added/removed. One thing that is tricky is that in the new manifest spec the manifest URL is meaningless. In order to update an icon we need to re-download the HTML file and see what manifest URL it points to. This is especially problematic if the user "pinned the website" rather than "pinned the page", i.e. if we bookmarked the start_url rather than the current page URL. What do we do if the page on the start_url doesn't link to a manifest? Or links to a different manifest? Does the spec address this? I definitely am hoping that the entire navigator.mozApps API goes away. At least I don't see any needs for it for FirefoxOS. > * activities Yeah, the system app needs to use the notifications mentioned above to track when a website gets pinned and that website uses a manifest which contain activity data. > * appcache_path (I guess we will deprecate this, but we might want to > replace it with service worker integration) I don't think this is needed. The user has visited the website anyway, and so the appcache should have already been installed. > * customizations (I guess we can keep this for the manifests of addons) I'm not sure what you mean by "customizations". But yes, I'm sure we'll need APIs for managing the list of installed addons exposed to various gaia apps, like settings and system app. And we'll need to expose something to the amo website as well. > * datastores-owned/datastores-access (I hope we can deprecate DataStore > eventually but we need it for now) I'm hoping that we can deprecate DataStore as well. In the meantime I don't think we should expose it to privileged content. Hence I think we can do whatever we need to here in order to keep allowing Gaia to work. No need to be overly concerned about the APIs. > * 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 not sure what you mean by this. But if needed we can automatically grant websites some permissions when they are pinned. Not sure if we'll do this in gecko or in gaia. I don't think that matters really, we should do whatever's easiest to implement. / Jonas _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
