User:DCamp/OfflineApps Security Review: Difference between revisions

User:DCamp/OfflineApps Security Review (view source)

716 bytes added , 2 October 2007

Confirmed users

673

edits

@@ Line 13: / Line 13: @@
 = Overview =
-''Describe the goals and objectives of the feature here.''
+For developers to make their applications available while the browser is offline, they need a few capabilities from the browser:
+* Guaranteed resource availability - All the application resources (images, html, script, etc) need to be locally available.  This is implemented in Fx3 as an additional HTTP cache (the "offline cache"), with eviction controlled by the application itself.
+* Offline data storage - The application needs to be able to store data on the user's machine.  globalStorage was available in Fx2, but needs to be extended for Fx3 to allow more space for offline apps.
+* Notification of when the browser is offline
+* Access to files from the &lt;input type="file"&gt; element.
 == Use Cases ==
@@ Line 22: / Line 27: @@
 == Schedule ==
-''Describe the rough schedule here, linking back to relevant product release milestones, as well as linking to any build/release notes.''
+* Preliminary &lt;link rel="offline-resource"&gt; support landed in alpha 3.
+* A sqlite-based store for the offline cache landed in alpha 5.
+* Additional javascript APIs landed in M7.
+* UI is planned to land in M9.
 == UI Design Documentation ==