Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Fixing malformed hyperlinks

Browse Source 
One hyperlink used the {@docRoot} tag even though it's a link to
a separate site (AOSP), so the link didn't work. Two other (internal)
links began with a slash instead of {@docRoot}, which kinda works
but isn't how we do things.

I'll build and test (and post the stage link in my first comment) but
if it looks good I'll go ahead and +2/merge it myself, since there
are no prose changes.

bug: 25755465
Change-Id: I11af855ed7a1e4a12ced7d0d7f6d5a4705c66811
This commit is contained in:
Andrew Solovay
2015-11-22 12:41:27 -08:00
parent f9d7645355
commit e68f6cdabd
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/html/guide/topics/security/permissions.jd
View File

@@ -76,7 +76,8 @@ ad hoc access to specific pieces of data.</p>
<p>This document describes how application developers can use the
security features provided by Android. A more general <a
href="http://source.android.com/tech/security/index.html"> Android Security
href="http://source.android.com/tech/security/index.html"
class="external-link">Android Security
Overview</a> is provided in the Android Open Source Project.</p>
@@ -98,7 +99,7 @@ require, and the Android system prompts the user for consent.</p>
<p>The application sandbox does not depend on the technology used to build
an application. In particular the Dalvik VM is not a security boundary, and
any app can run native code (see <a href="/sdk/ndk/index.html">the Android
any app can run native code (see <a href="{@docRoot}tools/sdk/ndk/index.html">the Android
NDK</a>). All types of applications &mdash; Java, native, and hybrid &mdash;
are sandboxed in the same way and have the same degree of security from each
other.</p>
@@ -114,9 +115,9 @@ signed by a certificate authority; it is perfectly allowable, and typical,
for Android applications to use self-signed certificates. The purpose of
certificates in Android is to distinguish application authors. This allows
the system to grant or deny applications access to <a
href="/guide/topics/manifest/permission-element.html#plevel">signature-level
href="{@docRoot}guide/topics/manifest/permission-element.html#plevel">signature-level
permissions</a> and to grant or deny an application's <a
href="/guide/topics/manifest/manifest-element.html#uid">request to be given
href="{@docRoot}guide/topics/manifest/manifest-element.html#uid">request to be given
the same Linux identity</a> as another application.</p>
<a name="userid"></a>
@@ -806,7 +807,7 @@ methods.</p>
<dd>Information about Android works on different types of devices and an introduction
to how you can optimize your app for each device or restrict your app's availability
to different devices.</dd>
<dt><a href="{@docRoot}http://source.android.com/devices/tech/security/index.html"
<dt><a href="http://source.android.com/devices/tech/security/index.html"
class="external-link">Android Security Overview</a></dt>
<dd>A detailed discussion about the Android platform's security model.</dd>
</dl>