aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUnsuk Jung <unsuk@google.com>2015-09-18 19:04:15 +0000
committerAndroid (Google) Code Review <android-gerrit@google.com>2015-09-18 19:04:15 +0000
commit4496f985fac9280d49a69a492d0faac816c3f695 (patch)
treeb20460aeacc5ac7c1433d8e90eb9d6bc0dd72c01
parent4727603e65c6fd80b25eadc0096acc512be35700 (diff)
parent4bbf74049a14efe1838d99df15d8feebb0d5b0fe (diff)
downloadsource.android.com-4496f985fac9280d49a69a492d0faac816c3f695.tar.gz
Merge "CDD: add requirement to enforce single runtime permission UI." into mnc-dev
-rw-r--r--src/compatibility/android-cdd.html7
1 files changed, 7 insertions, 0 deletions
diff --git a/src/compatibility/android-cdd.html b/src/compatibility/android-cdd.html
index ee588e11..057e214b 100644
--- a/src/compatibility/android-cdd.html
+++ b/src/compatibility/android-cdd.html
@@ -4129,6 +4129,13 @@ described in the SDK documentation; no permissions may be omitted, altered, or
ignored. Implementations MAY add additional permissions, provided the new
permission ID strings are not in the android.* namespace.</p>
+<p>Permissions with a protection level of dangerous are runtime permissions. Applications
+with targetSdkVersion > 22 request them at runtime. The system MUST show a dedicated UI for the
+user to decide whether to grant the requested runtime permissions and also provide a UI for the
+user to manage runtime permissions. On the system there MUST be one and only one
+implementation of both the UI for the user to accept runtime permissions and the UI for
+the user to manage runtime permissions.</p>
+
<h2 id="9_2_uid_and_process_isolation">9.2. UID and Process Isolation</h2>