This is a tracking bug for implementing app-cache integration with the .install() call. The behavior we want from an API point of view is: 1. Store calls the .install() function 2. If needed, the firefox asks the user if installing is ok. 3. Firefox downloads the manifest and finds the URL of the appcache manifest (possibly by checking the manifest attribute of the app's start page) 4. Firefox creates a new profile folder for the XULRunner app which will be used to run the app. 5. Firefox starts downloading the resources listed in the appcache manifest and saves them in the newly created profile folder 6. As resources are downloaded, progress events are delivered to the store.
Nominating for k9o - This relates to integrating app cache to the install flow of web apps to enable part of a k9o user story through app cache support (https://wiki.mozilla.org/Kilimanjaro/ProductDraft#The_Mozilla_web_platform_will_include_core_features_for_developing_games.2C_social.2C_productivity.2C_and_media_apps)
No need to block on this bug, we'll block on bug 760365 instead.
Other than bug 760067, is there anything left here that we absolutely need to do? I don't think bug 744713 is a must-have, though it would be very nice to have.
Would be great to have verified that we have all the pieces that we need here for the initial release for apps: * At installation the appcache resources are downloaded. * During download, progress events are sent to the store through the app object. * As soon as the app icon appears on the desktop, that the app can be started without network connectivity. I.e. all resources should be available through the appcache.
(In reply to Jonas Sicking (:sicking) from comment #4) > Would be great to have verified that we have all the pieces that we need > here for the initial release for apps: > > * At installation the appcache resources are downloaded. > * During download, progress events are sent to the store through the app > object. > * As soon as the app icon appears on the desktop, that the app can be > started without > network connectivity. I.e. all resources should be available through the > appcache. The preloading testing of bug 760365 I think already tested this. In verifying bug 760067, I'll keep a look out for this to make sure this definitely works.
Created attachment 642234 [details] gaping [comment deleted by admin]
Comment on attachment 642234 [details] gaping Please don't spam mozilla's bugzilla server with this. For testing, use landfill.
The content of attachment 642234 [details] has been deleted by Dave Miller [:justdave] <firstname.lastname@example.org> who provided the following reason: attachment was vandalism The token used to delete this attachment was generated at 2012-07-14 09:33:09 PDT.
Jonas, is this work still targeting desktop support as well or are you focused on just the B2G implementation?
(In reply to Ragavan S [:rags] from comment #9) > Jonas, is this work still targeting desktop support as well or are you > focused on just the B2G implementation? It works on both!
Yup, I think we can close this one.
This doesn't work on Firefox/Android, however, as far as I can tell.
I think this doesn't work anymore on desktop. I'll investigate a bit and file a new bug.
(In reply to Marco Castelluccio [:marco] from comment #13) > I think this doesn't work anymore on desktop. I'll investigate a bit and > file a new bug. It works, it's just the cache directory that has changed on Linux :)