From 03bf5c7a73c1640b7561b13220d032f596e20e6a Mon Sep 17 00:00:00 2001 From: Scott Main Date: Mon, 10 May 2010 11:08:26 -0700 Subject: [PATCH] docs: remove allowBackup attribute from documentation Change-Id: I377c354af77c6b915d35c7e374bae03020063856 --- docs/html/guide/topics/manifest/application-element.jd | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/docs/html/guide/topics/manifest/application-element.jd b/docs/html/guide/topics/manifest/application-element.jd index 08f35e96ba38..786223fcc4a9 100644 --- a/docs/html/guide/topics/manifest/application-element.jd +++ b/docs/html/guide/topics/manifest/application-element.jd @@ -3,8 +3,7 @@ page.title=<application>
syntax:
-
<application android:allowBackup=["true" | "false"]
-             android:allowClearUserData=["true" | "false"]
+
<application android:allowClearUserData=["true" | "false"]
              android:allowTaskReparenting=["true" | "false"]
              android:backupAgent="string"
              android:debuggable=["true" | "false"]
@@ -49,15 +48,6 @@ cannot be overridden by the components.
attributes
-
{@code android:allowBackup}
-
Whether the application allows its data to be backed up through the Android -Backup Manager — "{@code true}" if it does, "{@code false}" if not. By -default this attribute is "{@code true}". If an application declares this -attribute to be "{@code false}" the Backup Manager will never attempt to -perform any backup or restore operation, even if the application declares a -valid {@code android:backupAgent} attribute in its -manifest. -
{@code android:allowClearUserData}
Whether or not users are given the option to remove user data — -- 2.11.0